Skip to content
This repository was archived by the owner on Nov 5, 2019. It is now read-only.

Seems to be having issues with source-maps #3

Closed
lmartins opened this issue May 31, 2014 · 2 comments
Closed

Seems to be having issues with source-maps #3

lmartins opened this issue May 31, 2014 · 2 comments

Comments

@lmartins
Copy link

I have a little repo where im doing some testing to Webpack features.
One issue I haven't been able to solve is related source-maps for js files loaded using this webpack loader.

You can check the structure im describing next in the aforementioned repo, available at:
https://github.com/lmartins/WebpackBuildComponent

Webpack is processing the files like this

src/js/
   main.js - Entry point
   testeScriptLoader.js - Loaded with script-loader
   moduleA.js - Normal webpack require
   moduleB.js - Normal webpack require
   moduleC.js - Loaded using code splitting 

After setting up the project in Chrome Devtools and running Webpack, I get:
https://www.dropbox.com/s/2lo1ekw4xdzeuej/Screenshot%202014-05-31%2020.23.19.png

Every file seems to be accessible from devtools, meaning that I can click the source column edit and save the file, except for the file loaded using script-loader testeScriptLoader.js. For that file only, the source-map seems to be failing.

Any ideias?

@sokra
Copy link
Member

sokra commented Jun 1, 2014

Chome devtools workspace feature is currently not supported. By luck it works for some files. This will be part of webpack/webpack#238.

@lmartins
Copy link
Author

lmartins commented Jun 6, 2014

Thank you. Closing this as it is already mentioned in other issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants