-
Notifications
You must be signed in to change notification settings - Fork 2k
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
CSS SourceMaps busted #26190
Comments
@flootr and I have been looking at this. It appears that If we remove |
Doesn't affect style.css and style-debug.css, but css-loader recently added some things that may help with sourcemaps there: webpack-contrib/css-loader#901 |
Relevant PostCSS issues: |
This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels. |
This issue is stale because it has been 180 days with no activity. You can keep the issue open by adding a comment. If you do, please provide additional context and explain why you’d like it to remain open. You can also close the issue yourself — if you do, please add a brief explanation and apply one of relevant issue close labels. |
👋 Hey folks! Since this issue has been inactive for quite some time, KitKat has made the decision to close it.
If you think this issue warrants another look, here are some next steps!
Thanks for your involvement! |
The CSS source maps for
style-debug.css
are no longer pointing back to the original sass files. Instead, they seem to be pointing to the CSS that comes out ofnode-sass
.Reported by @jancavan
The text was updated successfully, but these errors were encountered: