Reputation: 9839

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

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..

Upvotes: 55

Answers (14)

chrisbyte

Reputation: 1608

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

Upvotes: 0

Animesh

Reputation: 1

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

Upvotes: 0

Mujibur Rehman Ansari

Reputation: 663

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.

Upvotes: 13

anna condal

Reputation: 41

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

Upvotes: 1

Manas

Reputation: 11

Switching Node version to 12.18.x worked for me.

Upvotes: 1

Rhett Harrison

Reputation: 11

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

Upvotes: 1

antimatter

Reputation: 872

I did below to resolve the issue.

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

Upvotes: 49

Mihir Ajmera

Reputation: 127

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.

Upvotes: 3

NexGen

Reputation: 130

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

Upvotes: 5

Anusuya Goud

Reputation: 171

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

Upvotes: 13

Abhi Patel

Reputation: 224

try this, add/modify your package.json

"node-sass": "*",

and run

npm install

Upvotes: 1

Adnan Sheikh

Reputation: 806

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

Upvotes: 10

Fatimah

Reputation: 732

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

Upvotes: 13

user2240097

Reputation: 311

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

Upvotes: 17

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

Answers (14)

Related Questions