Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

@koale/useworker is published to NPM without sourcemaps #138

Closed
marklawlor opened this issue Jul 10, 2023 · 0 comments · Fixed by #144
Closed

@koale/useworker is published to NPM without sourcemaps #138

marklawlor opened this issue Jul 10, 2023 · 0 comments · Fixed by #144
Assignees
Labels
bug Something isn't working
Milestone

Comments

@marklawlor
Copy link

marklawlor commented Jul 10, 2023

[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=code

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants