-
Notifications
You must be signed in to change notification settings - Fork 65
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
Cannot make sourcemaps work #40
Comments
@sqal which version of gulp-sass do you use? |
@w0rm 2.0.1. But is sass version relevant here? Sourcemaps only does not work with postcss in the task, as I mentioned before. |
@sqal it may be, if the relative file name doesn't match the one specified in the sourcemap that is coming from the sass, then sourcemaps won't be combined. |
Hmm OK. But i also tested it with only one scss file, outcome was the same - postcss breaks sorucemaps :( |
Probably this is connected with dlmanning/gulp-sass#106 |
@sqal can you create a minimal project that reproduces this issue? |
Maybe this issuw is relevant to postcss/autoprefixer#453 |
@ai my idea is to check that Perhaps a glob pattern |
@w0rm here you go: https://github.com/sqal/gulp-postcss-issue-40 |
Awesome, thanks, I'll look into it tonight
|
@sqal works perfectly fine for me https://yadi.sk/i/GsfUZ1OJgtKDt |
@w0rm That's weird. This is what it looks like to me: Why I don't have path to .scss file but .css? however i can still edit .scss file in sources panel (chrome), doesn't work in Firefox at all. I think this is not working properly, right? |
@sqal maybe it is a limitation of Firefox or has something to do with how browserSync does its live updates. The source map is generated properly. |
Closing this, because live updates and browser edit features are not related to gulp-postcss, and the correct sourcemap file is generated. |
Hmm.. but this is what it looks like in FF when gulp-postcss is on http://prntscr.com/79perd (can't edit scss), and this is when it's off (can edit) http://prntscr.com/79pgcq am i wrong or not? because to me looks like something doesn't work correctly after all. |
@sqal cannot see your screenshots. |
@w0rm Sorry for that.. with gulp-postcss - https://www.dropbox.com/s/0tkv2ow9clfr6zm/LRR32yD.png |
@sqal since its working in Chrome, might be a Firefox issue. I downloaded recent Firefox, tried to reproduce, but couldn't. Screencast: https://yadi.sk/i/5D9I3FxtgtQWs |
@w0rm I have the latest version of Firefox. Maybe this is Windows related issue? Perhaps someone with Windows 7 can confirm this issue? |
@sqal sorry I can't help you with this. If you want to verify source maps, remove browserSync, generate style.css and style.css.map, link to the css from a static html file, then open html file in the browser. If you don't see scss there, then you have style.css and style.css.map that are not working in your version of Firefox. |
@w0rm browser-sync has nothing to do with that, gulp-postcss seems to be still the problem, but all right, I give up on this.Thank you for your time anyway :) |
If you have just three files, test.html style.css and style.css.map, then this might be reduced test case for the Firefox. |
@sqal I might give it a try tomorrow. Will try to download windows7 from modern.ie. |
@sqal I can see app.scss in the recent Firefox for Windows 7. |
Hi everyone. I am fighting to get sourcemaps working with gulp-postcss plugin but I've run out of ideas, and don't know how to fix it. My sass task looks like this:
Above config generates app.css.map file in destination directory as it should but sourcemaps does not works in browser. Here you can see that source map file (broken): https://gist.github.com/sqal/f894149870da902707f8 However If i remove postcss from my task, everything works as it should: https://gist.github.com/sqal/d3328b6c283ddbfee88f
Is there some bug in postcss or am I missing something here? Any hints on why it is not working for me would be greatly appreciated :) Thanks.
// Forgot to mention. I am using gulp-postcss 5.1.6, gulp-sourcemaps 1.5.2 and autoprefixer-core 5.1.11
The text was updated successfully, but these errors were encountered: