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
I am opening this issue as a reminder, as the bug doesn't reside in gulp-sass but only affects it.
The problem occurs when there are constructs like
$someVar: '.className';
#{$someVar} {
//...
}
which results in
".className" {
//...
}
Which won't be interpreted by the css parsers.
It's kind of difficult to spot at first, as it depends on your scss and can affect only a fe rules with no error output during compile.
Issue is coming from node-sass 3.4 and referenced at sass/node-sass#1217 which in turn leads to an issue in libsass referenced at sass/libsass#1624
Everything is fine when using node-sass 3.3.3 but the recent bump of gulp-sass to 2.1.0 forced the node-sass version to "^3.4.1", imposing this bug on all users.
I hope this helps others facing the same issue.
The text was updated successfully, but these errors were encountered:
I am opening this issue as a reminder, as the bug doesn't reside in gulp-sass but only affects it.
The problem occurs when there are constructs like
which results in
Which won't be interpreted by the css parsers.
It's kind of difficult to spot at first, as it depends on your scss and can affect only a fe rules with no error output during compile.
Issue is coming from node-sass 3.4 and referenced at sass/node-sass#1217 which in turn leads to an issue in libsass referenced at sass/libsass#1624
Everything is fine when using node-sass 3.3.3 but the recent bump of gulp-sass to 2.1.0 forced the node-sass version to "^3.4.1", imposing this bug on all users.
I hope this helps others facing the same issue.
The text was updated successfully, but these errors were encountered: