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.

Should work after `gulp-sass` updates the dependency to `node-sass` https://github.com/sass/node-sass/issues/1484 — Pete TNT, May 19 '16 at 17:16
@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) — Pete TNT, May 19 '16 at 17:32
@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. — Pete TNT, May 19 '16 at 18:09

score 327 · Answer 1 · answered Jun 07 '16 at 22:07

327

run npm rebuild node-sass

or

run sudo npm rebuild node-sass

answered Jun 07 '16 at 22:07

Michael Vieth

3,442
1
11
6

10

This worked very well for the similar error in my Mac OSX environment! – Rahul Desai Oct 12 '16 at 19:01
20

Btw. It could happened, when you updated your NodeJS and node-sass was compiled with previous NodeJS version. – Garrett Nov 24 '16 at 15:24
7

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' – Simon_Weaver Jun 02 '17 at 18:58
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! – Simon_Weaver Jun 02 '17 at 18:59
4

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? – k2snowman69 Aug 18 '17 at 22:47
Worked for me too… But presumably this is a bug in the build system? – andrewf Nov 17 '17 at 21:34
Nah, it just happens when NodeJS is upgraded to to C++ addons. – Esteban Morales Jul 28 '18 at 03:09
yea it's working for me.. i think because node-saas need syncronize with latest of new parts from latest version of node.js.. – Iam ByeBlogs Dec 10 '18 at 10:36
Unfortunately this doesn't seem to help this very similar error: https://github.com/laradock/laradock/issues/1898 – Ryan Jan 16 '19 at 14:56
`npm rebuild node-sass` worked great for me in Kubuntu 20.04 – Leonardo Brambilla Oct 05 '22 at 22:22

score 136 · Answer 2 · edited Aug 08 '19 at 08:11

136

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

edited Aug 08 '19 at 08:11

Nickon

9,652
12
64
119

answered Jul 19 '16 at 19:33

Jorge Torres

1,806
1
11
6

2

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 – Pablo Cegarra Sep 02 '16 at 11:53
2

This worked on Mojave. No need to run `npm rebuild node-sass` – Amir Saleem Oct 08 '19 at 13:10
I do not know, how it works. But it worked for me like a charm. Thanks a lot – Alok Ranjan Sep 14 '20 at 06:42
This worked for me. – Patrick S Oct 26 '21 at 06:40

Khan Sharukh · Answer 3 · 2021-12-21T13:30:07.363

52

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

edited Dec 21 '21 at 13:30

answered Aug 09 '19 at 07:32

Khan Sharukh

1,151
12
21

score 43 · Answer 4 · answered Jul 11 '19 at 08:37

43

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 node-sass@4.12.0

answered Jul 11 '19 at 08:37

Sashi

2,659
5
26
38

3

Better to use `npm install node-sass@latest` – Ashraf Slamang May 05 '20 at 09:12
working perfectly in the way suggested with node@12 – The Mechanic Nov 22 '20 at 08:47
1

This is how my issue also got solved! Thank you @Sashi for sharing! – Manish Gupta Nov 07 '22 at 14:20

Balram Singh · Answer 5 · 2023-04-21T05:45:51.280

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 the compatibility table of the node with node-sass:-

NodeJS | Supported node-sass version | Node Module
Node 19     8.0+                        111
Node 18     8.0+                        108
Node 17     7.0+                        102
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/

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? — Dazag, Oct 06 '21 at 11:07
The magic combo for me was going back to node @ 12.22.8. This allowed node-sass to install fine. — Dicer, Jan 01 '22 at 21:41

score 10 · Answer 6 · answered May 25 '21 at 16:22

10

Kindly change your node version and use a stable version of node. This happened with me when I was trying with node version 15+ and npm version 7+. I changed my node version to 14.0.0 simply using nvm.

try:

nvm use 14.0.0

then:

npm run start or node-sass

answered May 25 '21 at 16:22

Arpit Tomar

101
1
2

`nvm install 12.18.2` -- this work for me. – Waket Zheng Jan 06 '22 at 15:56

Prasanth Louis · Answer 7 · 2021-10-25T14:58:55.673

8

You should also check your version of nodejs. I was on a version 9 of node js which isn't officially supported at this time of writing. Reverting back to version 6.11.4 fixed the issue for me.

edited Oct 25 '21 at 14:58

answered Nov 17 '17 at 14:36

Prasanth Louis

4,658
2
34
47

Node 8 also will work. You can get node 8 from https://npm.taobao.org/mirrors/node/v8.12.0/ node-v8.12.0-x64.msi – David Nov 28 '18 at 00:00

score 8 · Answer 8 · edited Nov 03 '22 at 11:26

8

If you are using arch-linux environment, You can uninstall node-sass using the command below:

npm uninstall --save-dev node-sass

then install sass using the comand below:

npm add -D sass

or

yarn add -D sass

am sure it works like a charm.

yarn add _D sass

** Great it works for me **

edited Nov 03 '22 at 11:26

SHUBHAM SONI

3
1

answered Jan 18 '22 at 10:38

Lamech Desai

709
6
11

score 6 · Answer 9 · answered Apr 25 '17 at 05:23

6

I don't know if this applies here, but for me, I just removed node_modules and reinstalled (npm install). Issue was fixed.

answered Apr 25 '17 at 05:23

abelabbesnabi

1,819
1
16
21

score 5 · Answer 10 · answered Jul 03 '18 at 14:03

5

npm install or npm rebuild node-sass

fixes the problems

please refer: https://github.com/sass/node-sass/issues/1764

answered Jul 03 '18 at 14:03

Fuat

789
9
14

score 4 · Answer 11 · answered May 27 '19 at 10:44

4

Go the path where node-sass is present and run this command

npm rebuild node-sass --force

This solved my issue

answered May 27 '19 at 10:44

rams

309
3
15

score 3 · Answer 12 · answered Jan 17 '18 at 09:38

3

That worked for me:

sudo npm cache clean -f
sudo npm install -g n
sudo n 6.0.0

answered Jan 17 '18 at 09:38

Andrei Todorut

4,260
2
17
28

For anyone wondering what `n` is, [click here](https://www.npmjs.com/package/n). Quote: _Node.js version management: no subshells, no profile setup, no convoluted API, just **simple**. (Unfortunately `n` is not supported on Windows yet.)_ – ADTC Feb 08 '18 at 17:59

score 3 · Answer 13 · answered Aug 28 '19 at 10:34

Error I was getting, Module "build failed: Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (72)".

First, tried:

npm rebuild node-sass

nothing helpful, then tried

sudo npm install --unsafe-perm -g node-sass

Worked like a charm

score 3 · Answer 14 · answered Sep 09 '21 at 09:22

We had this problem on several OS. Considering node-sass is deprecated, we simply migrated to Dart Sass based on this how to migrate from node-sass to dart sass and this In Vue CLI how do I use sass instead of node-sass (default for sass-loader)? (we have a vueJS project) and it works. We did:

npm install -D sass-loader sass

delete node-sass in package.json

npm prune

score 2 · Answer 15 · answered Nov 26 '21 at 16:18

I'm using wsl 2 with Ubuntu-20.04 and was facing this problem. You have to downgrade your node version as node-sass (at this moment) doesn't work with version 17 (latest) and even version 16 (stable). However, switching to version 14 helped me.

Run these commands

sudo npm install -g n

sudo n 14.17.5

score 1 · Answer 16 · answered Dec 11 '18 at 15:01

I had the same issue for windows x64 Platform.

Just updated the package.json with newer version of node-saas instead rebuild because in order to rebuild you need visual studio build environment which is suck to install for a dependency :)…

go with latest node-saas you should be fine:

"node-sass": "^4.11.0",

score 1 · Answer 17 · answered Nov 17 '20 at 17:19

Probably a node version issue.

Check your node version with

node -v

you can install node version manager to make life easier. See

https://github.com/nvm-sh/nvm#install--update-script

Install:
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.34.0/install.sh | bash

Usage: 
nvm install <version>       Download and install a <version> 
nvm use <version>           Modify PATH to use <version> nvm ls        
List versions (installed versions are blue)

score 1 · Answer 18 · answered Jul 22 '21 at 18:01

1

Only solution Work For macOs and Window

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

answered Jul 22 '21 at 18:01

abhinavsinghvirsen

1,853
16
25

score 1 · Answer 19 · answered Aug 25 '21 at 16:01

Node-sass incompatibility with the node version was the issue in my case. I had node-sass v4.13.1 with node version 14+ running in my machine. On seeing the release tag, I found that node version 14+ was not supported. So using the nvm I downgraded my node to 13+ and it worked.

score 1 · Answer 20 · answered Nov 20 '21 at 04:37

1

In my case, I had to bump down to node 12 from node 16

answered Nov 20 '21 at 04:37

Bhaskar

1,838
1
16
29

score 1 · Answer 21 · answered Apr 21 '22 at 22:21

1

Just make sure your shell has npm loaded.

I didn't find this answer here. I kept hitting this intermittently until I realized, my shell doesn't auto-load nvm - and so, when I ran build I'd hit this.

HTHs someone.

answered Apr 21 '22 at 22:21

Kevin Friedheim

394
3
15

score 0 · Answer 22 · answered Jul 29 '18 at 11:53

0

Remove node_modules/node-sass folder & run npm install (this may take some time based on the dependencies) then run npm run build

This should resolve the issue

answered Jul 29 '18 at 11:53

user1991251

81
1
1
3

score 0 · Answer 23 · answered Oct 06 '18 at 06:58

0

npm uninstall node-sass

npm i node-sass@4.7.2

https://dev.to/letsbsocial1/node-sass-and-node-910-4ol

answered Oct 06 '18 at 06:58

Kruti Choksi Patel

399
2
6

score 0 · Answer 24 · answered Dec 29 '18 at 20:23

0

Remove node modules: $rm-rf node_modules

Re install node modules: $npm install

answered Dec 29 '18 at 20:23

MCMatan

8,623
6
46
85

score 0 · Answer 25 · answered Jun 22 '19 at 05:49

0

If uninstall & install node-sass did not work try to remove node_modules folder and npm install

answered Jun 22 '19 at 05:49

Masoud Darvishian

3,754
4
33
41

nscalf · Answer 26 · 2019-08-22T02:38:25.003

0

npm i @ionic/app-scripts Was the only thing that had any impact for me.

edited Aug 22 '19 at 02:38

answered Aug 22 '19 at 02:33

nscalf

528
5
10

score 0 · Answer 27 · answered Mar 07 '20 at 21:08

0

npm audit fix works for me like a charm!

answered Mar 07 '20 at 21:08

samivic

1,216
14
13

score 0 · Answer 28 · answered Dec 24 '20 at 09:41

0

Its just a version issue Install node version 10 it will work fine

npm install node@10

answered Dec 24 '20 at 09:41

Mohamed Imran

149
1
5

score 0 · Answer 29 · answered Jan 25 '21 at 06:23

0

I had the same issue.none of the solutions worked.So I tried my usual response of restarting my mac which I do quite rarely and the issue got resolved. When you dont shutdown or restart your Mac for a long time,such random issues occur.

answered Jan 25 '21 at 06:23

U R

490
9
15

score 0 · Answer 30 · answered Nov 13 '21 at 16:08

0

Install dart-sass

npm install node-sass@npm:sass

answered Nov 13 '21 at 16:08

Saleh

57
1
3

score 0 · Answer 31 · answered Nov 23 '21 at 19:13

0

had to downgrage nodejs according to supported version table https://www.npmjs.com/package/node-sass

answered Nov 23 '21 at 19:13

Илья Вайнер

29
3

score 0 · Answer 32 · answered Dec 03 '21 at 03:14

https://github.com/sass/node-sass

I check the version table in the repo and modify the node-sass version in the dependencies in the package.json file according to the node version.

  "dependencies": {
    "node-sass": "4.14.0",
  }

a quick guide for minimum and maximum supported versions of node-sass:

score 0 · Answer 33 · answered Jan 25 '23 at 10:24

0

In case of Node v16.19.0 and Ubuntu 22.04.1 LTS I've updated sass-loader to "^13.2.0" version.

"sass-loader": "^13.2.0",

answered Jan 25 '23 at 10:24

zhovtyj

61
1
3

score 0 · Answer 34 · answered Feb 20 '23 at 11:25

yarn upgrade helped me.

After this in my react app I started to get another error "Uncaught ReferenceError: process is not defined" - then: yarn add react-scripts@latest helped me finally to run this FE app (scripts were updated from 3.0.1 ver to 5.0.1)

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

34 Answers34

Linked

Related