The deployed module doesn't seem to follow current nodejs conventions

[julienw]

See import-js/eslint-plugin-import#2098 (comment) for more insight.

[ljharb]

Specifically, if you want the package to be requireable/importable, you need to specify "main" and "exports".

[mstange]

This module was produced by wasm-pack, and I think I even filed this very bug at some point: rustwasm/wasm-pack#94
Maybe I never repackaged after the fix. I'll try that.

[mstange]

Updating the dependencies and building with wasm-pack build --out-name index fixes this. I'm currently testing the output and will release a new version soon.

[mstange]

@ljharb I've published 0.3.0 with the main file now being named index.js. The package.json still doesn't specify any "exports" and I'm not sure what's meant by that - I don't see an "exports" key on these package.json docs.
Is the new version at https://unpkg.com/browse/gecko-profiler-demangle@0.3.0/ correct or does it need more changes?

[ljharb]

You don't really need the "exports" field here, because in this case there's only one .js file in the package.

It looks fine to me, but it really should include "main": "./index.js" to be explicit.

[mstange]

Thanks for the feedback! I filed rustwasm/wasm-pack#1009 on that. However, given the current maintainership status of wasm-pack, it probably won't see any action any time soon. I'll adjust the package.json manually in the meantime.

[mstange]

Ok, fixed in https://unpkg.com/browse/gecko-profiler-demangle@0.3.1/ .

[julienw]

Thanks for the quick update @mstange :-)