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
This means that sourcemap generation fails for scss-files that contain an & in selector, such as &.mod-enabled or &:after
Until that bug is fixed it would be great to have the option of disabling sourcemap generation through options to gulp-sass, instead of it assuming you want them generated whenever the sourcemap plugin is present:
Yes, however, that makes no difference, when i set it. Also, looking at the condition, i do not believe that it is even used, that option.
The documentation clearly states that the default value is undefined, and that sourcemaps will be generated when the value is === true, or the type of the value is string, so if i do not set that option at all, sourcemaps should not be generated. They are anyway, and failing.
There is currently a bug in libsass: sass/libsass#2312
This means that sourcemap generation fails for scss-files that contain an
&
in selector, such as&.mod-enabled
or&:after
Until that bug is fixed it would be great to have the option of disabling sourcemap generation through options to
gulp-sass
, instead of it assuming you want them generated whenever the sourcemap plugin is present:Am i reading the code correctly? I am still a gulp/nodejs novice.
Even after the bug in libsass is fixed, it would be nice to have the option to disable sourcemap generation through options.
My suggestion is this: reload@1724bee
Then setting
sourceMap: false
ingulpfile.js
will disable sourcemap generation.Additional information:
OS: Alpine Linux
The text was updated successfully, but these errors were encountered: