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

node.jsSassArchlinuxGulp SassNode Sass

node.js Problem Overview


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.

node.js Solutions


Solution 1 - node.js

run npm rebuild node-sass

or

run sudo npm rebuild node-sass

Solution 2 - node.js

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

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

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

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/

Solution 6 - node.js

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.

Solution 7 - node.js

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

Solution 8 - node.js

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 

Solution 9 - node.js

npm install or npm rebuild node-sass

fixes the problems

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

Solution 10 - node.js

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

npm rebuild node-sass --force

This solved my issue

Solution 11 - node.js

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

Solution 12 - node.js

That worked for me:

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

Solution 13 - node.js

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

Solution 14 - node.js

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 https://stackoverflow.com/questions/61198331/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

Solution 15 - node.js

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

Solution 16 - node.js

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",

Solution 17 - node.js

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)

Solution 18 - node.js

Only solution Work For macOs and Window

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

Solution 19 - node.js

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.

Solution 20 - node.js

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

Solution 21 - node.js

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

Solution 22 - node.js

Solution 23 - node.js

Remove node modules: $rm-rf node_modules

Re install node modules: $npm install

Solution 24 - node.js

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

Solution 25 - node.js

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

Solution 26 - node.js

npm audit fix works for me like a charm!

Solution 27 - node.js

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

npm install node@10   

Solution 28 - node.js

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.

Solution 29 - node.js

Install dart-sass

npm install node-sass@npm:sass

Solution 30 - node.js

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

Solution 31 - node.js

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:

Solution 32 - node.js

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.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionJitendra VyasView Question on Stackoverflow
Solution 1 - node.jsMichael ViethView Answer on Stackoverflow
Solution 2 - node.jsJorge TorresView Answer on Stackoverflow
Solution 3 - node.jsKhan SharukhView Answer on Stackoverflow
Solution 4 - node.jsSashiView Answer on Stackoverflow
Solution 5 - node.jsBalram SinghView Answer on Stackoverflow
Solution 6 - node.jsPrasanth LouisView Answer on Stackoverflow
Solution 7 - node.jsabelabbesnabiView Answer on Stackoverflow
Solution 8 - node.jsArpit TomarView Answer on Stackoverflow
Solution 9 - node.jsFuatView Answer on Stackoverflow
Solution 10 - node.jsramsView Answer on Stackoverflow
Solution 11 - node.jsLamech DesaiView Answer on Stackoverflow
Solution 12 - node.jsAndrei TodorutView Answer on Stackoverflow
Solution 13 - node.jsNandyView Answer on Stackoverflow
Solution 14 - node.jsMattSoulView Answer on Stackoverflow
Solution 15 - node.jsAbdullah ChView Answer on Stackoverflow
Solution 16 - node.jsEmrah MehmedovView Answer on Stackoverflow
Solution 17 - node.jsDanTheMannView Answer on Stackoverflow
Solution 18 - node.jsabhinavxeonView Answer on Stackoverflow
Solution 19 - node.jsBipul Bikram ThapaView Answer on Stackoverflow
Solution 20 - node.jsBhaskarView Answer on Stackoverflow
Solution 21 - node.jsuser1991251View Answer on Stackoverflow
Solution 22 - node.jsKruti Choksi PatelView Answer on Stackoverflow
Solution 23 - node.jsMCMatanView Answer on Stackoverflow
Solution 24 - node.jsMasoud DarvishianView Answer on Stackoverflow
Solution 25 - node.jsnscalfView Answer on Stackoverflow
Solution 26 - node.jssamivicView Answer on Stackoverflow
Solution 27 - node.jsMohamed ImranView Answer on Stackoverflow
Solution 28 - node.jsU RView Answer on Stackoverflow
Solution 29 - node.jsSalehView Answer on Stackoverflow
Solution 30 - node.jsИлья ВайнерView Answer on Stackoverflow
Solution 31 - node.jsuser17384367View Answer on Stackoverflow
Solution 32 - node.jsKevin FriedheimView Answer on Stackoverflow