-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
3.5.1 introduces a breaking change #1459
Comments
This project is just an implementation of the Sass language. It aims to be This is happening because your Sass is not valid. As the message says This previously worked due to a bug in LibSass which was fixed in latest
|
I just had the same. In my case it's grunt-sass which downloaded the dependency. But suddenly my existing tags don't build anymore! I have a mixin defined inside a @if not mixin-exists block which is apparently not allowed anymore. Also variables defined inside @if not variable-exists now seem to be only valid within that block unless declared global. It may be that these have been seen as bug fixes ("we weren't interpreting the sass spec properly, now we are" but they should still be flagged as breaking changes - by making the interpretation much stricter you are breaking stuff which worked. And should therefore have been a version which did not come as "compatible" according to npm. |
@xzyfer : yeah, I guessed that. But this much stricter is still a breaking change - even if a "breaking bug-fix" |
To be clear this was never allowed but it mistakenly worked. This is no different to depending on an undocumented API. For that reason we do not consider these breaking changes. If valid Sass started breaking we would consider that a breaking change. We don't claim responsibility for bugs in the Sass code being compiled. |
That makes sense @xzyfer . Thank you for a quick response. |
Same issue here, but OK, I understand that this is a bug and it worked mistakenly. So is it possible to get a “legal” conditional import (in my case |
Conditional imports are not possible in Sass.
|
So sad. OK, thank you @xzyfer. I will search a workaround. |
...since 3.5.1 breaks @import inside of @if: sass/node-sass#1459
A fix to node-sass has made this illegal: sass/node-sass#1459 Fixes canonical#1016
Our build server just downloaded latest version of gulp-sass (2.3.0) which in turn downloaded node-sass 3.5.1. This caused a previously unseen critical error in the code that wasn't touched since January:
Message:
Relevant code:
https://github.com/brainly/style-guide/blob/42136dd914ea0626cc76f7d1a39ee37bf836c376/src/sass/_mixins.scss#L88
Last successful build was using version node-sass@3.4.2.
The text was updated successfully, but these errors were encountered: