Node Sass does not yet support your current environment: Linux 64-bit with false

Question

Getting this error on Arch Linux with node-sass. I'm using it with gulp-sass.

Node Sass does not yet support your current environment: Linux 64-bit with false

Versions

$ gulp -v
[19:43:15] CLI version 3.9.1
[19:43:15] Local version 3.9.1

$ npm -v
3.9.0

Node

$ node -v
v6.2.0

Even using this command npm rebuild node-sass is not changing anything.

Solution 1

run npm rebuild node-sass

or

run sudo npm rebuild node-sass

Solution 2

in some cases you need to uninstall and install node-sass library. Try:

npm uninstall --save-dev node-sass

and

npm install --save-dev node-sass

Solution 3

I managed to solve this issue using the command below.

npm audit fix - Worked for me

npm audit fix

I tried - Didn't work for me

sudo npm rebuild node-sass

Then I tried - Didn't work for me

npm uninstall --save-dev node-sass
npm install --save-dev node-sass

Solution 4

As of July 2019 with Node v12 -

node-sass v4.11.0 doesn't work with Node 12.

I faced this problem when I upgraded node to v12.

Rebuilding node-sass as suggested by the other answers didn't work as well.

Upgrading node-sass to v4.12.0 fixed it for me.

npm install [email protected]

Solution 5

Uninstall and reinstall node-sass and it will find missing binary for itself.

npm uninstall --save-dev node-sass
npm install --save-dev node-sass

If issue is not resolved using above commands, there may be problem with your node version. Check that your node version supports node-sass version. Chose a stable node version and repeat above commands to fix this issue.

Below is compatibility table of node with node-sass:-

NodeJS | Supported node-sass version | Node Module
Node 16     6.0+                        93
Node 15     5.0+                        88
Node 14     4.14+                       83
Node 13     4.13+, <5.0                 79
Node 12     4.12+                       72
Node 11     4.10+, <5.0                 67
Node 10     4.9+, <6.0                  64
Node 8      4.5.3+, <5.0                57
Node <8     <5.0                        <57

If issue is still not fixed, check node-sass supported environment's list:- https://github.com/sass/node-sass/releases/

View more solutions

Comments

[antjanus]

I have the same issue. What node version are you using btw?

[Jitendra Vyas]

@antjanus Updated to the question.

[Pete TNT]

Should work after gulp-sass updates the dependency to node-sass github.com/sass/node-sass/issues/1484

[Jitendra Vyas]

@PeteTNT What could be the solution till then?

[Pete TNT]

@JitendraVyas you could try updating your node-sass manually with npm install node-sass (or by forking the gulp-sass and bumping up the version in the package.json)

[Jitendra Vyas]

@PeteTNT I have already tried this npm rebuild node-sass

[Pete TNT]

@JitendraVyas Rebuild node-sass doesn't update the version, just rebuilds the binaries and such from the existing versions. Run npm install node-sass first.

[Jitendra Vyas]

@Pete TNT - Even that didn't work

[TiyebM]

npm uninstall node-sass npm install [email protected]

[Pablo Cegarra]

Not working for me Node Sass could not find a binding for your current environment: Linux 64-bit with Node.js 4.x Found bindings for the following environments: - Linux 64-bit with Node.js 6.x

[Rahul Desai]

This worked very well for the similar error in my Mac OSX environment!

[Garrett]

Btw. It could happened, when you updated your NodeJS and node-sass was compiled with previous NodeJS version.

[aruno]

can anyone explain why this works? will this need to be done every time I clear out my node_modules folder? or is sass installed as some kind of global 'service'

[aruno]

also I'm very confused how a clean install in June 2017 (on Windows) leads to this error when Node 6 came out over a year ago? why wasn't this just a temporary error at the time. this solution did work for me - but I really would like to understand why!

[k2snowman69]

Documentation for npm rebuild says "This command runs the npm build command on the matched folders. This is useful when you install a new version of node, and must recompile all your C++ addons with the new binary.". I know I started hitting this after upgrading node, so maybe that's the same for everyone else here?

[Umut Çağdaş Coşkun]

Worked for me. I guess this is the answer.

[andrewf]

Worked for me too… But presumably this is a bug in the build system?

[ADTC]

For anyone wondering what n is, click here. Quote: Node.js version management: no subshells, no profile setup, no convoluted API, just simple. (Unfortunately n is not supported on Windows yet.)

[Esteban Morales]

Nah, it just happens when NodeJS is upgraded to to C++ addons.

[David]

Node 8 also will work. You can get node 8 from npm.taobao.org/mirrors/node/v8.12.0 node-v8.12.0-x64.msi

[Iam ByeBlogs]

yea it's working for me.. i think because node-saas need syncronize with latest of new parts from latest version of node.js..

[Ryan]

Unfortunately this doesn't seem to help this very similar error: github.com/laradock/laradock/issues/1898

[Amir Saleem]

This worked on Mojave. No need to run npm rebuild node-sass

[Ashraf Slamang]

Better to use npm install node-sass@latest

[Alok Ranjan]

I do not know, how it works. But it worked for me like a charm. Thanks a lot

[The Mechanic]

working perfectly in the way suggested with node@12

[Dazag]

This did it for me! Don't know why if you don't specify the version it will install the latest one but not the one that better suits your environment, is that the normal approach for npm?

[Patrick S]

This worked for me.

[Houssem TRABELSI]

it works for me great

[Dicer]

The magic combo for me was going back to node @ 12.22.8. This allowed node-sass to install fine.

[Waket Zheng]

nvm install 12.18.2 -- this work for me.