-
-
Notifications
You must be signed in to change notification settings - Fork 430
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
sourceMappingUrl is wrong #81
Comments
Is the URL wrong or is the map file just not generated? |
I think both, it should generate for example: styles.sourcemap.css.map (in stead of sass.map?) |
You're right. It looks like this has changed in webpack somehow... need to investigate. |
+1 |
With the current
The later
When deleting the first line manually everything looks fine in the browser. |
Thx for investigating this.... so maybe we just need to remove all the |
That could be a solution, though I haven't tested other configurations. Removing this line does not work, as the map from |
Well, that option doesn't make sense from libsass' point of view ^^ |
Forgive me if I'm an idiot, but isn't there already an option for that? |
Adding if (opt.sourceMap) {
…
opt.sourceMap = this.options.output.path + '/sass.map';
+ opt.omitSourceMapUrl = true;
} works fine for me. |
I'll try that out, thanks! |
Will this be added to the official distribution at some point? |
Fix for issue #81 - sourceMappingUrl is wrong.
Yep. See #123 |
Thanks! |
Same problem here as #58, even when devtool = source-map.
Just tried to run the demo test/sourceMap too, which isn't working either:
The file sass.map isn't generated. I'm using node-sass 3.0.0-beta.5 and sass-loader 1.0.1 and also tried other versions. Any ideas?
The text was updated successfully, but these errors were encountered: