←back to thread

272 points abdisalan | 2 comments | | HN request time: 0.426s | source
1. JansjoFromIkea ◴[] No.42183792[source]
node-sass is to blame for like 95% of these node-gyp issues in my experience, it's not that much grief to deal with but it's hard to grasp how it was allowed to hang around so terribly for so long
replies(1): >>42184377 #
2. pier25 ◴[] No.42184377[source]
> it's hard to grasp how it was allowed to hang around so terribly for so long

It's not hard. The explanation is simply that the dart version of SASS (the sass npm package) is much slower than node-sass.

At one point it was like 20x slower and I believe right now it's about 2-3x slower.

https://github.com/sass/dart-sass/issues/1534