Import directives may not be used within control directives or mixins

[ACastans]

Hi,

Since today i have this issue on my build.

I use gulp-sass and node-sass is a dependency of it.

I use in several place those kind of condition :

@if(#{$brand} == 'my-brand'){
@import '../../config/_config-my-brand';
}

I have not this issue if I fixed the "node-sass" dependency to "3.4.2" manually in the gulp-sass package.

But since it's incremented with the new version, I can't do anything.

I have see some similar issue but all are closed. Do you have an update on this ?

Regards.

Adrien.

[fuhlig]

It seems related to the 3.5.* update and can be fixed with the 3.4.* version as you stated. Had the same problem at several projects on our CI servers since yesterdays 3.5.* update

Fix:

• Remove your grunt-sass / gulp-sass
• set node-sass@3.4.2 in your (dev)dependencies
• $npm install

Hope this helps
Regards,
Flo

[ACastans]

@fuhlig Thanks it seem to make the quick fix.

@node-sass team, do you have a fix for this in the pipe ?

Regards.

Adrien.

[xzyfer]

This project is an implementation of the Sass language. Our goal is to be 100% compatible with Sass. These issues you mention are a result of invalid Sass. Node Sass assumes valid Sass is being compiled. 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.

If you wish to suggest features of file bugs in the Sass language please open an issue with Sass - https://github.com/sass/sass

In closing if your code does not compile with the official Sass project you should not expect it to compile with Node Sass.

[gorkamolero]

This isn't closed. The code compiles. Just try to compile bootstrap and see. Please open again.

[xzyfer]

I dont follow what you're saying

…

On 29 Jun. 2017 6:04 pm, "Gorka" ***@***.***> wrote: This isn't closed. The code compiles. Just try to compile bootstrap and see. Please open again. — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1471 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWO0P0gGF1VZqzUWpgY1VIPV663pXks5sI1qngaJpZM4INg4l> .

[randre70]

Please re-open.

This project is an implementation of the Sass language. Our goal is to be 100% compatible with Sass. These issues you mention are a result of invalid Sass. Node Sass assumes valid Sass is being compiled. This is no different to depending on an undocumented API. For that reason we do not consider these breaking changes.

See sass/libsass#1724

[xzyfer]

These are unrelated.

…

On Mon., 25 Mar. 2019, 8:38 pm randre70, ***@***.***> wrote: Please re-open. This project is an implementation of the Sass language. Our goal is to be 100% compatible with Sass. These issues you mention are a result of invalid Sass. Node Sass assumes valid Sass is being compiled. This is no different to depending on an undocumented API. For that reason we do not consider these breaking changes. See sass/libsass#1724 <sass/libsass#1724> — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#1471 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAjZWLW_AZwjhNUHwVSz-7J3ORbarZoSks5vaJkXgaJpZM4INg4l> .