fix: prioritize dart-sass over deprecated node-sass #402
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this do?
Prioritizes dart-sass (
sass
) overnode-sass
when both are availableWhy?
node-sass
is deprecated, as is its underlying LibSass.Modern Sass features such as
@use
cannot and will not be supported bynode-sass
In projects where both dependencies are available, this change will prevent the deprecated
node-sass
from running against modern SCSS code that may require dart-sass to compile.While a configurable option for the preferred loader would be a more robust solution, it would require much more extensive changes to the plugin. This is a simple solution that will resolve the core problems experienced in issues #321 and #304, and involves minimal changes to the plugin code, leveraging the already-existing functionality of having a priority-ordered list of Sass modules.