Maybe it could be solved by making a fork (since this package is **node-sass-**asset-functions )

Some people are now using dart-sass (or sass ) instead of node-sass, because of the painfulness caused by the native extension :(

Like sass-loader made itself sass-implementation-agnostic, it would be great to make node-sass-asset-functions also implementation-agnostic.

I found that node-sass-asset-functions itself runs well with sass, but even when I don't need node-sass as dependency, install node-sass-asset-functions forces my machine to rebuild node-sass.

2018年09月12日 23 35 19

How it should be like?

Taking sass module as a parameter

assetFunctions({
 ....
 implementation: require('node-sass') // or require('sass')
})
// or even...
assetFunctionsFor(require('node-sass'))({
 ....
})

Then drop node-sass from dependencies, and it allows users to avoid forced rebuilding node-sass.