-
Notifications
You must be signed in to change notification settings - Fork 380
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
Getting incorrect path with sourcemaps, am I doing something wrong? #498
Comments
I've tried a few different configurations of things, but I'm still getting the same behavior. Any advice? |
Have you tried using |
Yep my fix is the same, had to use |
the problem has not been solved? When i use |
outputStyle: compact doesn't work for me, either. :( |
@Sash-OK If you are running autoprefixer on your outputted Scss, I would expect it to break the associations between rules and the source maps. |
I'm seeing it break even without autoprefixer, using outputStyle: compact. That doesn't mean autoprefixer isn't breaking things, too, but it isn't the culprit in my case. |
@MattHoneycutt I think you should change to
I haven't payed close attention to Gulp Sass, but now I notice that sourcemaps are a different plugin rather than an option of Gulp Sass. (If this doesn't work, perhaps calling |
Also having this issue. Using |
Still waiting for a fix. @Dellkan , @MattHoneycutt - The first problem is bootstrap _breadcrumbs.scss. I opened an issue over there - twbs/bootstrap-sass#1105 Their variable interpolation value in
After you fix that issue, it appears that there is something gulp-sass has to fix because node-sass compiles everything fine (after fixing bootstrap issue) when running |
@Dellkan @MattHoneycutt I think I spoke too soon. I don't think it's a problem with gulp-sass anymore. I still had postcss running autoprefixer in the stream. When I commented that out and just ran gulp-sass with sourcemaps and So it seems like the problem is postcss or autoprefixer. Will update as I find out more. The bootstrap breadcrumbs issue still holds true though as it messes up libsass itself. |
I can confirm that simply commenting out the |
This is either an issue with libsass (used by gulp-sass), or another gulp plugin interfering. Comment out all other gulp-plugins. If the issue persists open an issue with libsass. |
Just wanted to add to this as well. I also have the issue with sourcemaps not matching up correctly, and can also confirm it is strictly happening when the |
For anyone digging around, the issue isn't with gulp-sass. It's a known issue. Libsass (maybe node sass) seems to still have a bug - sass/node-sass#957 Also, PostCSS isn't fully compatible with sass sourcemaps and the issue has been closed as won't fix (though he tried 👍) - postcss/postcss#926 |
I'm very new to this package, so it's quite possible I'm doing something wrong or that it isn't a gulp-sass issue. Any help, or a nudge in the right direction, is greatly appreciated. :)
That said:
I'm using gulp-sass with bootstrap-sass. I'm starting with a simple SCSS file, vendor.scss:
My custom.scss:
And my gulp task:
Everything builds, the resulting CSS is what I would expect, but the sourcemap is off for the style from my custom.scss. It seems to be "stuck" on the last file that was processed from bootstrap's package:
Any tips or suggestions?
The text was updated successfully, but these errors were encountered: