Proposal: Dart Sass Compatibility for meteor-scss

[illusionfield]

Proposal: Dart Sass Compatibility for meteor-scss

Hi everyone,

I've started working on a repository aimed at making the meteor-scss package compatible with Dart Sass. You can find my initial work here: illusionfield/meteor-scss.

Please note that this is still very much a work in progress, with a lot of experimentation and no documentation yet.

I'm looking for feedback from the community on whether this is a worthwhile direction to pursue. Could this be something that eventually leads to a merge request, or do you foresee any insurmountable issues or roadblocks that I might not have considered?

Looking forward to your thoughts!

thx
@illusionfield

[github-actions]

Thank you for submitting this issue!

We, the Members of Meteor Community Packages take every issue seriously.
Our goal is to provide long-term lifecycles for packages and keep up
with the newest changes in Meteor and the overall NodeJs/JavaScript ecosystem.

However, we contribute to these packages mostly in our free time.
Therefore, we can't guarantee your issues to be solved within certain time.

If you think this issue is trivial to solve, don't hesitate to submit
a pull request, too! We will accompany you in the process with reviews and hints
on how to get development set up.

Please also consider sponsoring the maintainers of the package.
If you don't know who is currently maintaining this package, just leave a comment
and we'll let you know

[illusionfield]

One of my ideas is to create a version of the plugin that acts purely as a bridge between the Sass compiler and Meteor. In this setup, developers could freely install the Dart Sass dependency via npm, depending on their preference (dart-sass or dart-sass-embedded). The plugin would detect and handle both, as each has a different compile method that offers better performance in specific cases.

This approach would make the Dart Sass dependency largely version-independent, requiring only compatibility checks between the plugin and specific Sass versions. Developers would have the flexibility to use whichever version of Sass they need, without relying on a specific version embedded in this package.

It would also significantly reduce the need for frequent version or patch updates for this package while maintaining flexibility for developers.

What do you think about this idea?