-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New release ^7.0.1 are not compatible with Node 16 #3297
Comments
What is the error? |
C:\Users\aryan\Downloads\npm>npm install node-sass npm ERR! A complete log of this run can be found in: |
node version - v16.17.0 |
Looks like there is something wrong with the binaries in on the new release. I'm investigating. |
Hi @xzyfer, |
I'm at a bit of a loss. I've re-uploaded the binaries. I've confirmed a manually downloaded binary works. But when the binary is downloaded from github as part of the install process it's corrupt. It's possible the broken binaries are cached somewhere along the way. The only thing I can think of is publishing a new release and hoping the binaries that are uploaded are fine. That should clear out any caches. |
That didn't work either. I created a v7.0.3 for testing locally with a known good binary. When the binary is downloaded it's corrupted. I'm at a loss. |
Oh my, I didn't realise how much was on master that was released in v7.0.2. I had intended to just release #3292. Looks like I also released untested changes to the binary download process. That gives me somewhere to look. |
This should be resolved in v7.0.3. |
I've also unpublished v7.0.2 to avoid further issues. |
Yes verified this issue has been resolved. npm install node-sass added 240 packages, and audited 241 packages in 41s |
Solved. |
@xzyfer same problem occurs again. 😢 node version used
|
After installing node-saas@7.0.3, above error was fixed on node:19.2 image. |
I have the same error with v9.0.0 🤔
|
I was getting this error with v9 on a fairly barebones new install of Ubuntu 22.04 (ARM64). Skimmed through the output, installed what seemed to be missing (
|
We are getting the error in production regarding node-sass.
Please guide.
In package.JSON we are using
"node-sass": "^7.0.1",
+7.0 version supported node 17 which already reached end-of-life (EOL). Please provide support for stable version.
The text was updated successfully, but these errors were encountered: