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
PostCSS reduces SourceMap #797
Comments
It will be fixed when we will tokenize values and selectors in 6.0. |
Great, thanks! |
Great to hear! We're shipping some awesome sass editing features in devtools and will be excited to demonstrate it working with autoprefixer in the pipeline. :) cheers |
@paulirish Will you be publishing how Less can be integrated into devtools editing? |
@matthew-dean perhaps! can you hook me up with a small less app with a watch task that I can try out? |
@paulirish You mean like: https://getcrunch.co/, the best Less & Sass editor/compiler app of all time in the history of human civilization? ... I might be biased. 👀 |
@matthew-dean I think he means a small website/app with styles written in less and a watch task in place via npm-scripts/grunt/gulp. |
Any news? |
@mischnic no news. We need very big refactoring which will bring only few features. This is why it is hard to find somebody to do this refactoring. |
Hi Andrey,
The autoprefixer/postcss turned out to output reduced sourceMap, i.e. it reduces the amount information in the initial sourcemap. The example repo is here: aslushnikov/autoprefixer-breaks-sourcemap
SourceMap without autoprefixer: sourceMap - notice how
red
sass variable is mapped to css property value.SourceMap with autoprefixer: sourceMap - notice how mapping is done property-wise.
Could this be fixed?
The text was updated successfully, but these errors were encountered: