-
Notifications
You must be signed in to change notification settings - Fork 353
-
Notifications
You must be signed in to change notification settings - Fork 353
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
Source mappings wrong when using compressed style #1896
Comments
Can you provide a minimal repo that reproduces this issue? |
Hi @nex3 Here is a link to a reproduction repo https://github.com/david10sing/minified-sass-breaking-sourcemap |
That repro looks like it passes the Sass output, including the sourcemap, through PostCSS. Can you reproduce it with Sass alone? |
Hi @nex3 Removed the postcss processing. As you will see, it has the same issue. I also renamed the class names so it's clearer. |
I can't reproduce that. Here's what I did: $ git clone https://github.com/david10sing/minified-sass-breaking-sourcemap
$ cd minified-sass-breaking-sourcemap
$ npm i
$ mkdir dist
$ node sass-compiler.js I then opened https://sokra.github.io/source-map-visualization/ and uploaded the generated |
It's not in chrome devtools inspector |
That sounds like a bug in the chrome devtools inspector. Have you tried reporting it there? |
Thank you @nex3 Reported ☝️ |
@david10sing That is not the right place for chrome bugs, please follow instructions on this page: https://www.chromium.org/for-testers/bug-reporting-guidelines/ |
Context
I am experiencing an issue when using the JS API,
sourcemap
compile option when used in tandem withstyle = compressed
.The source map is produced and I write it to a file. However, the mappings are broken and in Chrome's devtools, I am seeing styles pointing to the wrong file.
Screenshots
Wrong
Correct
Question
The text was updated successfully, but these errors were encountered: