-
Notifications
You must be signed in to change notification settings - Fork 385
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
Source maps and external libraries, wrong sources. #993
Comments
That's the given libraries' fault ;-) They should use the
|
Thanks for the fast response, Sébastien. I'll close this issue and open one in each of the libraries. |
Maybe this should be mentioned in the docs (not only the API)? I spent some time looking for that exact options |
@Nami-Doc Sure! Where do you think it would be best to put it? |
I first looked in the sbt plugin doc, so I'd say there. I'm not sure with what it'd go, though. Maybe there are other options you want to cover |
Maybe an additional section in sbt plugin doc for "Publishing libraries"? |
I'm not sure this should be cornered to library publishing? I'm hitting this issue on a local project, myself |
Ah? But for a local project, the source maps pointing to your local files should work, don't they? |
The EDIT: it seems scala-js-dom has
|
When using source maps with external libraries (it has happened to me both with scalatags and with scalajs-react), it seems like the file paths of the computer where the library build was done are being leaked.
Example of paths I'm finding when browsing the generated map file:
The text was updated successfully, but these errors were encountered: