You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This causes tools such as Webpack 5 to produce warnings as it tries to load the missing sourcemap file
Failed to parse source map from '/home/mark/project/node_modules/@koale/useworker/dist/index.mjs.map' file: Error
: ENOENT: no such file or directory, open '/home/mark/project/node_modules/@koale/useworker/dist/index.mjs.map'
If I clone the repo and run npm run build I can see that the .map files are generated. They are just not being published to NPM
[Required] Expected behavior
.map files are published to NPM
The text was updated successfully, but these errors were encountered:
[Required] Describe the bug
@koale/useworker
generates sourcemaps during the build process appending the sourcemap sourceMappingURL comment to each file.For example
dist/index.mjs
has the comment//# sourceMappingURL=index.mjs.map
However if you inspect the code published to NPM, it does not include the
.map
files https://www.npmjs.com/package/@koale/useworker?activeTab=codeThis causes tools such as Webpack 5 to produce warnings as it tries to load the missing sourcemap file
If I clone the repo and run
npm run build
I can see that the.map
files are generated. They are just not being published to NPM[Required] Expected behavior
.map
files are published to NPMThe text was updated successfully, but these errors were encountered: