-
-
Notifications
You must be signed in to change notification settings - Fork 433
Path is missing from source maps #8
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
Comments
Hey thanks for doing all of the hard work on this! Sorry for the delay in implementing it. This is published in v0.3.2. |
Ok, thanks, I just discovered an additional problem: Typescript places its own "//# sourceMappingURL=SomeFile.ts" in the JavaScript output. So the bundle.js files ends up with multiple "# sourceMappingURL" declarations. (Of course, only the last "# sourceMappingURL=bundle.js.map" is valid) It seems that Chrome does not care, but other tools do. (For example "NPM source-map-support") The solution is to remove the redundant and incorrect "sourceMappingURL" declaration. I added another line:
This solves the problem. |
I tried your loader in a test project and found out that the path is missing from the source maps.
For example:
end up in Chrome as:
I compared your loader with the jsx-loader and saw that the jsx-loader sets two additional properties on the sourcemap. (
sources
andfiles
)I changed your code and it works now: (basically a copy from jsx-loader)
Does this look ok to you?
Could you incorporate this change in your code and npm module?
Thanks!
The text was updated successfully, but these errors were encountered: