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 is a hacky syntax that css-modules uses to define dependecies across files, in general we'd want sass to ignore it, which is what the other sasses do.
:import("./foo") {
color: red;
}
Actual results
libsass 3.5.4
InvalidCSSafter":import(": expected selector,was'"./foo") {'online 1 at column 1
Expected result
This is what dart and ruby sass compile to
:import("./foo") {
color: red;
}
The text was updated successfully, but these errors were encountered:
ruby also allows this. Ideally (for me) libsass would NOT error. I was expecting it to behave more like css parsers and just ignore stuff it doesn't understand. I realize why sass might not do that tho. In our case this is more about being compatible with the very limited pseudo syntax css-modules requires
Happy to try and fix this myself. Dug into it a bit and generally identified where to make the change, but can't figure out how to consume the the content, or what it should be stored in, same as css custom property value?
I'll add that i'm a JS dev not a Cpp one, so please excuse me if I'm making some obvious blunder !
jquense
added a commit
to jquense/libsass
that referenced
this issue
Sep 16, 2019
input.scss
This is a hacky syntax that
css-modules
uses to define dependecies across files, in general we'd want sass to ignore it, which is what the other sasses do.Actual results
libsass 3.5.4
Expected result
This is what dart and ruby sass compile to
The text was updated successfully, but these errors were encountered: