node-sass is always required upon require('gulp-sass'). This means when node-sass isn't working (eg. it isn't on node 11 yet right now), one can't use sass.compiler = require('dart-sass') because require('gulp-sass') itself will fail.
> const sass = require('gulp-sass')
[20:46:36] Error: Node Sass does not yet support your current environment:
Windows 64-bit with Unsupported runtime (67)
Could gulp-sass conditionally require node-sass inside the main function? This would be a breaking change since require('gulp-sass').compiler would be undefined until the gulp stream's started — but since it's currently not possible to use a different compiler without requiring the default one, it may very well be worth it.
This has been discussed before. It isn't currently planned. It's always
been possible to change compiler.
If you specifically just want to use dart sass you can try gulp-dart-sass.
On Sat., 27 Oct. 2018, 11:02 am MaurÃcio Kishi, notifications@github.com
wrote:
node-sass is always required upon require('gulp-sass'). This means when
node-sass isn't working (eg. it isn't on node 11 yet right now), one
can't use sass.compiler = require('dart-sass') because
require('gulp-sass') itself will fail.const sass = require('gulp-sass')
[20:46:36] Error: Node Sass does not yet support your current environment:
Windows 64-bit with Unsupported runtime (67)Could gulp-sass conditionally require node-sass inside the main function?
This would be a breaking change since require('gulp-sass').compiler would
be undefined until the gulp stream's started — but since it's currently
not possible to use a different compiler without requiring the default one,
it may very well be worth it.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dlmanning/gulp-sass/issues/715, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjZWDmAWITLq4hLg5VJ-a022haYerBNks5uo6KTgaJpZM4X9Ie-
.