Compliance with dart sass? about gridle HOT 5 CLOSED

Hi there,
First thanks for your interest in gridle and thanks for your feedback.
I'm not aware of dart sass so I cannot tells you more on that for now. I have to make tests etc...
I can encourage you to use node-sass as a replacement cause It works very well and is very performant.
I will investigate on dart sass but I can't promise you that I will make big changes to gridle for that. Will see

from gridle.

Hi Olivier,

So far ruby sass has been working pretty well for me. Dart-sass was new to me as well, but appears to be the go-to direction. The sass site links to it as standalone installation, and npm and chocolatery installation methods also appear to be pulling from some dart image.
My issues above were specifically with the standalone installation for Windows, but it could be that these other installation methods have the same effect.

You can read about it on the sass blog: http://sass.logdown.com/posts/7081811

In the meantime I will see if I can get node-sass up and running (thanks for the suggestion :) ).

from gridle.

Since dart-sass is the new reference implementation, griddle should be made compatible with it, in my opinion. We use griddle in some of our projects, and we can't modernise our build tooling because of this problem.

Maybe you can add a warning in the readme about the dart-sass incompatibility for now?

from gridle.

The issue here is that Gridle make heavy use on silent classes that are scoped (initialized) inside a media query and dart sass seems to doesn't care about that and set these silent classes in the root scope. Then when I try to extend one of these silent classes from inside a media query, the error listed above pops up. As this is a core principle of Gridlev3, it will be difficult to rearrange the code to make it work with these sass implementations.
By the way, I will release Gridle v4 (in release candidate for now) soon. It will be a little bit different and a lot simpler so I hope this will be a kind of answer to your issues

from gridle.

Hello, just to add a bit more information and a little question : now in 2022, "node-sass" is explicitly marked as deprecated, so the compiler to use is de facto "sass" (means dart sass) who is the one following the standard (for ex math.div instead of "/" as described https://sass-lang.com/documentation/breaking-changes/slash-div). Many frameworks already changed and only work with "sass" and never with "node-sass". So this is not an option at all.

As a consequence, I understand that the only solution is to use Gridle 4 ? (which compiles ok with "sass" ?)

But what if we have production code with Gridle 3, and absolutely can't change all the architecture to use Gridle 4 and just updated npm/gulp stack and… all broken 'cause new versions can't compile Gridle 3 ? :(

I will try to downgrade all versions of the stack gulp etc, until all compile again…

from gridle.