-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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 map URLs shouldn't be prefixed with a local path #4518
Comments
I wonder where this message origin in Could you run it with |
Hi @sokra, I tried with
|
I'm not too worried about that though because it just seems to be wrapping the underlying error which is:
I submitted a PR to loader-utils to stop the prefixing, that's where that was happening: Unfortunately I'm still getting the same errors, just the prefix has been correctly removed:
|
Looks like scalajs-bundler is using the source-map-loader. The source-map-loader uses webpack's resolver to resolve the source-map. webpack's resolver, however, cannot resolve remote resources via http and such. So, why are they using the source-map-loader at all? And: I'm also not sure if it's a good idea to point the |
add info about emitting an Error webpack#4518
add info about emitting an Error webpack#4518
We use source-map-loader to preserve (as most as possible) source-map continuity across libraries. |
Any update on this, guys? |
@webpack-bot move to webpack-contrib/source-map-loader |
I've moved it to webpack-contrib/source-map-loader. |
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
Some libraries (i.e. nearly all created via Scala.JS) have URLs in their source maps. However when being used with webpack, webpack is prepending a
./
to all the URLs results in trillions of warnings like this:And resulting in a final source map that no longer works for those libraries.
If the current behavior is a bug, please provide the steps to reproduce.
Setup any dummy project with Scala.JS and scalajs-bundler which runs everything through webpack.
What is the expected behavior?
Source map links that can be identified as absolute URLs should be used as is, without modification.
I believe the fix would be a very simple test like this before prepending:
https://github.com/jantimon/html-webpack-plugin/pull/619/files
Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Using webpack 2.2.1, Node.JS 7.7.3.
The text was updated successfully, but these errors were encountered: