Closed mclrc closed 1 year ago
I think Dart Sass support can be enabled by creating a new custom compiler, probably by sub-classing the included SCSS
compiler (see libsass.SCSS
for an example).
I don't mind including that new compiler to the project and you're welcome to work on a PR.
I'm planning to include this in the next release, but I don't have an ETA yet. I'd appreciate if someone created a working PR work that, this may speed things up.
Ruby Sass has reached EOL and the official Sass website only provides instructions for installing the NPM package (Dart Sass) Due to these lines in
scss.py
sass
is being passed--sourcemap
, with an argument, eitherauto
ornone
which is incompatible with Dart Sass.This results in an error during compilation which is hard for a consumer to pinpoint, as it is simply a
StaticCompilationError
without any further information.The only reason I figured out what the problem was and which version of
sass
was expected is because I had a look at the docker image used for the tests. If switching to Dart Sass is currently not desirable, I think clarifying the expected version ofsass
in the docs would be a very good idea as I (and presumably others) would have been able to fix my problem much quicker.With minor changes, e. g. passing either
--no-source-map
or--source-map
, theStaticCompilationError
s cease and everything behaves as expected. There may be other compatibility issues between Dart and Ruby Sass, but I haven't encountered any in my use. If you like, I could start work on a PR.I apologize if I missed something in the docs or anything like that, I'm quite new to all this.
Thanks for this great library, and have a nice day!