Skip to content
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

Closed
blowery opened this issue Jul 19, 2018 · 6 comments
Closed

CSS SourceMaps busted #26190

blowery opened this issue Jul 19, 2018 · 6 comments

Comments

@blowery
Copy link
Contributor

blowery commented Jul 19, 2018

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 of node-sass.

Reported by @jancavan

@blowery
Copy link
Contributor Author

blowery commented Jul 19, 2018

@flootr and I have been looking at this. It appears that postcss isn't able to handle the sourcemap that's coming out of node-sass.

If we remove postcss from the build chain, the sourcemap does appear to work, but we lose autoprefixer's work.

@blowery
Copy link
Contributor Author

blowery commented Mar 12, 2019

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

@blowery
Copy link
Contributor Author

blowery commented Mar 12, 2019

Relevant PostCSS issues:
postcss/postcss#1211
postcss/postcss#797

@github-actions
Copy link

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.

@github-actions
Copy link

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.

@cuemarie
Copy link

👋 Hey folks! Since this issue has been inactive for quite some time, KitKat has made the decision to close it.

  • Internal reference, for more on this decision: pdqkMK-14B-p2

If you think this issue warrants another look, here are some next steps!

  1. Report anew: A new report with more current details and steps to replicate may be the best way to renew attention on this issue. Feel free to refer back to this closed issue in your report!
  2. Reopen: If you feel the issue still matches the context/history here, you can also reopen the issue and add fresh logs, screenshots and steps to reproduce.

Thanks for your involvement!

@cuemarie cuemarie closed this as not planned Won't fix, can't repro, duplicate, stale Aug 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants