You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have unicode symbols anywhere in your Sass (eg: pseudo element content property), it will cause the sourcemap to not appear in Chrome when using gulp-sourcemaps with gulp-sass + gulp-autoprefixer.
It seems to be just the symbols, if you replace them with hex representations then sourcemaps work.
It also appears to be autoprefixer related as compiling with symbols but without autoprefixer does show the sourcemap correctly.
If you have unicode symbols anywhere in your Sass (eg: pseudo element
content
property), it will cause the sourcemap to not appear in Chrome when usinggulp-sourcemaps
withgulp-sass
+gulp-autoprefixer
.It seems to be just the symbols, if you replace them with hex representations then sourcemaps work.
It also appears to be autoprefixer related as compiling with symbols but without autoprefixer does show the sourcemap correctly.
I made a reduced test case which demonstrates the issue and has more detail here MethodGrab/gulp-sourcemaps-test-case.
Possibly related: #8
The text was updated successfully, but these errors were encountered: