Build Fails: `npm rebuild node-sass --force`

Question

Using n to switch Node versions. I've ran yarn, npm rebuild node-sass --force many many times. And still fails. Getting this error:

Node Sass could not find a binding for your current environment

This usually happens because your environment has changed since running `npm install`. Run `npm rebuild node-sass --force` to build the binding for your current environment.

Anyone have any idea how to fix?

Also.. When running this command..

npm rebuild node-sass --force

I get..

npm WARN using --force I sure hope you know what you are doing.

Doens't seem like it is doing anything..

What’s the rest of the error? There should be lots of output before that. — Ry-
– Ry- ♦, Commented Nov 2, 2018 at 20:17
Try to remove the entire node_module folder & reinstall it — felixmosh
– felixmosh, Commented Nov 2, 2018 at 20:18
Have you successfully built it before, or is this the first time? Also, what environment? Windows, Linux...? — Andy
– Andy, Commented Nov 2, 2018 at 20:27
I have encountered this before, specifically when moving from Windows to Linux. If this is the case, felixmosh is correct, but you need to run npm cache clean after deleting the node_module folder and before running npm-install. — Marvin WordWeaver Parsons
– Marvin WordWeaver Parsons, Commented Nov 2, 2018 at 20:28
You mean “npm WARN using --force I sure hope you know what you are doing.” is the only line of output? Do you have ignore-scripts=true in your .npmrc? — Ry-
– Ry- ♦, Commented Nov 3, 2018 at 1:40

lennartk · Accepted Answer · 2020-10-05 13:23:28Z

49

I did below to resolve the issue.

npm uninstall node-sass npm i node-sass npm rebuild node-sass

edited Oct 5, 2020 at 13:23

lennartk

6291 gold badge7 silver badges15 bronze badges

answered Jul 22, 2020 at 15:05

antimatter

8727 silver badges11 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Neha Prajapati Over a year ago

Try with --force if uninstallation is also failing npm uninstall node-sass --force npm install node-sass --force

AS Mackay · Accepted Answer · 2019-07-17 17:17:20Z

17

remove node-sass from your command and just run npm rebuild --force

edited Jul 17, 2019 at 17:17

AS Mackay

2,8559 gold badges21 silver badges27 bronze badges

answered Jul 17, 2019 at 17:00

user2240097

3114 silver badges13 bronze badges

Comments

Fatimah · Accepted Answer · 2019-10-27 15:19:26Z

If npm rebuild node-sass and npm rebuild node-sass --force doesn't work. Just uninstall node-sass and install again.

MartenCatcher · Accepted Answer · 2020-02-19 05:52:22Z

I have tried all options like:

npm rebuild --force npm rebuild node-sass --force npm rebuild node-sass &

also did try to install through Python & updated VS Project links, but nothing worked..

EXCEPT running it manually:

node node_modules/node-sass/scripts/install.js

danronmoon · Accepted Answer · 2022-07-09 00:36:46Z

The main issue is that your node-sass and node-npm versions are incompatible.

Please see the chart on this site or on this.

So my suggestion is either adjust your node-npm version or adjust node-sass.

In my case I was using node-sassof version 4.9.4 with node version 8.12.0 and npm version 6.4.1, It was working fine without any issue, later on I got new system and I had installed the latest node(12.16.0) & npm(6.13.4) and issue started so I dug into this and found above links.

Hope this will help you.

Adnan Rafique · Accepted Answer · 2019-11-18 07:52:27Z

10

I just ran the command npm install node-sass and my issue was resolved.

answered Nov 18, 2019 at 7:52

Adnan Rafique

8163 gold badges15 silver badges30 bronze badges

Comments

NexGen · Accepted Answer · 2020-06-30 10:37:51Z

5

remove package-lock.json file

remove node_modules folder

then remove from package.json it devDependencies

"node-sass": "4...",

then

npm i node-sass -D

and

npm i

answered Jun 30, 2020 at 10:37

NexGen

1301 silver badge3 bronze badges

2 Comments

doubleya Over a year ago

After several hours of messing with this issue, removing node_modules and package-lock.json was all I needed to do. After that npm rebuild node-sass finally worked for me.

Uwe Keim Over a year ago

Helped me, too. Thank you. I omitted step 3 (removing manually from package.json) and it still succeeded.

Mihir Ajmera · Accepted Answer · 2020-07-14 09:47:27Z

We are also facing the same issue many times, due to different versions of node and npm for numbers of web applications.

For that, we are just using the below command to take proper node-sass supported versions.

npm install node-sass or npm install node-sass -g

then try to rebuild the node-sass with,

npm rebuild node-sass or npm rebuild node-sass -f

After that all, if required then we can rebuild all packages and npm start or npm run watch and then the application is working properly.

Abhi Patel · Accepted Answer · 2019-12-30 10:43:33Z

1

try this, add/modify your package.json

"node-sass": "*",

and run

npm install

answered Dec 30, 2019 at 10:43

Abhi Patel

2241 silver badge6 bronze badges

Comments

Rhett Harrison · Accepted Answer · 2020-11-24 18:24:48Z

Uninstall and reinstall node-sass. Consider moving to dart sass because node-sass is now deprecated.

Manas · Accepted Answer · 2021-06-06 17:54:46Z

1

Switching Node version to 12.18.x worked for me.

answered Jun 6, 2021 at 17:54

Manas

114 bronze badges

1 Comment

Manas Over a year ago

The error said it found Binding for version 12.18.x, so when I switched to that node version it worked

anna condal · Accepted Answer · 2021-08-11 11:39:26Z

I solved it with npm rebuild node-sass --force, in my case I had to do it as sudo

Animesh · Accepted Answer · 2023-12-05 13:26:47Z

0

check your node version in pc & project node version. If it's different u will get the issue. The best way is to use nvm for different node projects

answered Dec 5, 2023 at 13:26

Animesh

1

2 Comments

geertjanknapen Over a year ago

Why is nvm the best way? How to check node versions? Adding information based on those two questions would drastically improve your answer.

Ram Chander Over a year ago

This does not provide an answer to the question. Once you have sufficient reputation you will be able to comment on any post; instead, provide answers that don't require clarification from the asker. - From Review

chrisbyte · Accepted Answer · 2024-10-03 14:29:43Z

I tried the suggestions above (rebuild, uninstall, reinstall, etc.) and was getting this error: Node Sass is no longer supported. Please use sass or sass-embedded instead.

I switched to sass and that fixed it for me. Didn't have to change anything else. My project is several years old and that's all I needed to do when trying to run it on a new machine.

npm uninstall node-sass npm i sass npm rebuild sass

Collectives™ on Stack Overflow

Build Fails: `npm rebuild node-sass --force`

14 Answers 14

1 Comment

Comments

Comments

1 Comment

Comments

Comments

2 Comments

Comments

Comments

Comments

1 Comment

Comments

2 Comments

Comments

Linked

Hot Network Questions

Collectives™ on Stack Overflow

14 Answers 14

1 Comment

Comments

Comments

1 Comment

Comments

Comments

2 Comments

Comments

Comments

Comments

1 Comment

Comments

2 Comments

Comments

Linked

Related