Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (57)

Question

Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (57)

SetCodesToFire opened this issue 7 years ago · 58 comments

I faced this issue when I used the latest LTS version of node.js i.e, 8.9.0 and npm version 5.5.1

I resolved this by updating the gulp-saas version number to 3.1.0 in the package.json file and it resolved, I wish you change the same :)

Answer 1 · 2017-11-07T12:35:39.000Z

I also noticed that many of you are having trouble with npm install. I made small research and found out that the used gulp-sass version "^2.0.4" in the devDependencies has a dependency of node-sass : "^3.4.2" which can be satisfied by version 3.13.1. But version 3.13.1 supports only node versions till 7 release v3.13.1
The easiest solution to the problem, which will save a lot of trouble for windows users with node versions 8 and 9, is to bump gulp-sass version to the latest "^3.1.0". It requires the latest node-sass release v4.6.0.

This way we avoid the need for building the module from source.

Note: There will be some warnings in the initial install, because of unmet optional dependencies.

Edit: The commit which fixes the problem was merged to the master branch and the issue #21 was closed.

Answer 2 · 2017-11-08T07:53:36.000Z

@s-slavchev what commands should I use to fix this? Or do I need to modify package.json? I'm on x64 too and I really want to solve this.

Answer 3 · 2017-11-08T08:05:50.000Z

@s-slavchev you just open your package.json file and in that you will see gulp-saas in the dev dependencies :::

Step 1:

"gulp-sass": "^2.0.4"

change this to

"gulp-sass": "^3.1.0"

step 2: now run
$ npm install
in the command prompt

done.

Now everytime you git hard reset,(according to the lecture and move to the other branches.) you will not have to npm install again and again and hence you are done with these two steps. 👍

Answer 4 · 2017-11-09T08:27:05.000Z

@SetCodesToFire thanks now it's working!

Answer 5 · 2017-11-15T15:34:11.000Z

Should be working now!

Answer 6 · 2018-01-04T07:25:09.000Z

Updating the gulp-saas version number to 3.1.0 solved the issue and works fine.
Thanks

Answer 7 · 2018-02-14T08:50:16.000Z

Updating the gulp-saas version number to 3.1.0 and run npm update (or if you are using yarn run "yarn upgrade" and problem solve)

Answer 8 · 2018-03-01T21:27:51.000Z

Updating to gulp-sass 3.1.0 solved the issue for me, too
Thanks

Answer 9 · 2018-03-14T14:19:13.000Z

Still working. Upgraded to gulp-sass 3.1.0 and solve my problem. Thanks!

Answer 10 · 2018-03-21T12:53:04.000Z

I spent 2 hours of updating/installing; Node, Npm, gulp, gulp-sass etc on my windows machine... nothing worked!! Till I found this and tried it. JESUS FREAKING CHRIST, YOU ARE A LIFE SAVER!

Answer 11 · 2018-03-22T14:33:01.000Z

You are LIFE saver ! THanks

Answer 12 · 2018-03-29T12:21:47.000Z

running npm rebuild node-sass also helps.

Answer 13 · 2018-03-31T18:03:51.000Z

This absolutely solved my problem. Trying to update my gulp-Sass!

Answer 14 · 2018-04-04T01:46:38.000Z

And, if you get the following error follow this -

"Could not load the Visual C++ component VCBuild.exe”

https://stackoverflow.com/questions/21658832/npm-install-error-msb3428-could-not-load-the-visual-c-component-vcbuild-ex

Answer 15 · 2018-04-11T01:52:17.000Z

running npm rebuild node-sass helped me... thanks a lot

Answer 16 · 2018-04-23T07:56:44.000Z

I dont have any gulp-sass, jsut sass and still have the error

Answer 17 · 2018-04-23T10:55:42.000Z

thank you, OMG this saved my ass haha

Answer 18 · 2018-04-25T18:39:28.000Z

please help me i changed on package.json to the v3.1.0 but i am still getting error

Starting 'sass'...
[20:32:45] 'sass' errored after 167 ms
[20:32:45] Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (57)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v3.13.1

Answer 19 · 2018-04-26T01:31:02.000Z

@SetCodesToFire thanks now it's working!

Answer 20 · 2018-05-12T10:54:17.000Z

@JMKP npm rebuild node-sass didn't work for me. I ran which node-sass and found out that node-sass was also installed via brew. I just deleted the file which node-sass was pointing to and reinstalled it via npm install -g node-sass. Hope that helps

Answer 21 · 2018-05-15T19:40:47.000Z

This error occurs when I try run Gulp in directory of my project that cloned by SmartGit. For other project's directories Gulp works fine! And npm rebuild node-sass and npm install -g node-sassdidn't work for me. BUT npm install node-sass (without -g) helped!

Answer 22 · 2018-05-24T05:40:03.000Z

@Titoratus I was also facing the same issue. Thank you for the solution. "npm install node-sass" worked for me

Answer 23 · 2018-06-08T13:36:18.000Z

You could also get this when you recently installed node.js on a fresh computer. Before you can update your node-sass, the following commands should be executed:

npm --add-python-to-path='true' --debug install --global windows-build-tools
npm config set msvs_version 2015
npm i node-sass@latest

Answer 24 · 2018-06-21T18:32:20.000Z

@WouterVanherck,

What does line 2 do? What do you set it as if you're using VS2017 or VS Code?

Answer 25 · 2018-06-22T16:58:36.000Z

@jrswenson,
Actually, besides the obvious which is setting the version, I'm not 100% sure what it does.
I just know that I had a generic error and Googled my way to a solution.
Execute the first command and check if that's enough, because that alone might fix it already.

As for the VS2017/VS Code question:
That command helped me fix my issue, even if I'm using VS2017 an VS Code too.
Thinking about it, might as well do --msvs_version=2017 instead.

Let me know if it works out and good luck coding!

Answer 26 · 2018-07-03T08:58:12.000Z

npm install node-sass works for me.Thanks a lot~

Answer 27 · 2018-07-13T14:22:05.000Z

try to delete node_modules and node-sass from package.json dependencies

and after that run npm install node-sass

Answer 28 · 2018-07-30T10:26:29.000Z

npm install node-sass works for me.Thanks a lot~

Answer 29 · 2018-08-14T09:15:08.000Z

you should run: npm i node-sass --save-dev once again

Answer 30 · 2018-10-25T18:56:16.000Z

here's what worked for me on macOS:

Downgrade node from "11.0.0 Current" to "8.12.0 LTS", (https://nodejs.org/en/)

following these instructions to downgrade:
https://apple.stackexchange.com/questions/171530/how-do-i-downgrade-node-or-install-a-specific-previous-version-using-homebrew#answer-262119

then npm rebuild node-sass

and it worked

Answer 31 · 2018-10-31T01:47:28.000Z

@Titoratus I was also facing the same issue. Thank you for the solution. "npm install node-sass" worked for me

worked for me too

Answer 32 · 2018-11-06T10:46:42.000Z

I did the steps which are here:
https://github.com/dlmanning/gulp-sass/wiki/Update-to-the-latest-Gulp-Sass

then it worked for me

Answer 33 · 2018-11-08T13:52:40.000Z

This error appears on new versions of Node js (> 8.0.0 ). Switching to version 8 solves the problem.
In my case nvm use 8.12.0

Answer 34 · 2018-11-13T00:13:58.000Z

The error happens when you have the latest version of node js. The solution was to update the project with npm update.

Answer 35 · 2018-11-13T19:57:42.000Z

npm rebuild node-sass thanx.

Answer 36 · 2018-12-13T17:50:37.000Z

gulp-sass update worked like a treat.
Thanks!

Answer 37 · 2019-01-16T12:17:55.000Z

This error occurs when I try run Gulp in directory of my project that cloned by SmartGit. For other project's directories Gulp works fine! And npm rebuild node-sass and npm install -g node-sassdidn't work for me. BUT npm install node-sass (without -g) helped!

npm install node-sass works for me.Thanks a lot~

@antonioribeiro

Answer 38 · 2019-02-12T11:53:47.000Z

Updating to gulp-sass 3.1.0 solved the issue for me, too
Thanks

Confirmed - it helped relatively to ZURB Emails: "gulp-sass": "^2.1.0" => "gulp-sass": "^4.0.0"

Answer 39 · 2019-03-05T11:19:36.000Z

npm rebuild node-sass didn't help
helped:
npm uninstall node-sass
npm install node-sass

Answer 40 · 2019-03-07T03:42:44.000Z

here's what worked for me on macOS:

Downgrade node from "11.0.0 Current" to "8.12.0 LTS", (https://nodejs.org/en/)

following these instructions to downgrade:
https://apple.stackexchange.com/questions/171530/how-do-i-downgrade-node-or-install-a-specific-previous-version-using-homebrew#answer-262119

then npm rebuild node-sass

and it worked

Worked for me on windows too.

Answer 41 · 2019-03-11T02:45:46.000Z

I resolve my problem make this tip down:

Tip for windows users, uninstall node-sass and reinstall (npm install node-sass) and then build (npm build) and run the application (npm serve -open)

Answer 42 · 2019-07-02T01:37:39.000Z

Fixing with an Ionic angular application.

Node v12.2.0 Windows 10.

Build failed with error code: 1 but I ignored this as it later said "Binary is fine"

npm uninstall node-sass
npm uninstall node-sass -g
npm install node-sass
npm build
ionic serve

Answer 43 · 2019-09-20T20:20:22.000Z

Please run sudo npm rebuild node-sass from terminal and please don't forgot the sudo before using command.

Above command resolved my issue!!

Answer 44 · 2019-09-23T06:45:07.000Z

I have same problem, so i update to "gulp-sass": "^3.1.0", so i got error
TypeError [ERR_INVALID_CALLBACK]: Callback must be a function at makeCallback (fs.js:136:11) at Object.utimes (fs.js:1094:14) at C:\xampp\htdocs\github\dungphanxuan\yiiframework.com\node_modules\gulp-touch\index.js:11:13 at wrappedMapper (C:\xampp\htdocs\github\dungphanxuan\yiiframework.com\node_modules\map-stream\index.js:84:19) at Stream.stream.write (C:\xampp\htdocs\github\dungphanxuan\yiiframework.com\node_modules\map-stream\index.js:96:21) at Pumpify.ondata (C:\xampp\htdocs\github\dungphanxuan\yiiframework.com\node_modules\readable-stream\lib\_stream_readable.js:619 :20) at Pumpify.emit (events.js:198:13) at Pumpify.EventEmitter.emit (domain.js:466:23) at addChunk (C:\xampp\htdocs\github\dungphanxuan\yiiframework.com\node_modules\readable-stream\lib\_stream_readable.js:291:12) at readableAddChunk (C:\xampp\htdocs\github\dungphanxuan\yiiframework.com\node_modules\readable-stream\lib\_stream_readable.js:2 78:11)

Answer 45 · 2019-09-30T07:27:44.000Z

This error occurs when I try run Gulp in directory of my project that cloned by SmartGit. For other project's directories Gulp works fine! And npm rebuild node-sass and npm install -g node-sassdidn't work for me. BUT npm install node-sass (without -g) helped!

npm install node-sass worked!!!

Answer 46 · 2019-11-14T13:05:47.000Z

When i used the node version 13.1. i had the error "Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime"

When i installed the version < 13 the problem has fixed.

Answer 47 · 2019-11-21T13:00:16.000Z

you should run: npm i node-sass --save-dev once again

good people still exist in this world

Answer 48 · 2019-11-28T09:02:31.000Z

After I update node.js to 13.2.0, I suffer this error["Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (75) ***not same as 57 in this question title], but I don't remember the last vesion of node.js, so I uninstall node.js 13.2.0, try other versions. At last, I go back to node.js 10.17.0 version, I solve this problem.

Answer 49 · 2019-12-02T18:04:13.000Z

@LiamKarlMitchell That did the trick for me 👍.
I have node-sass as devDependency so I used this:

npm uninstall node-sass
npm uninstall node-sass -g
npm install node-sass -D

Answer 50 · 2019-12-06T18:08:32.000Z

I got the same error after updating Node.js to v13.3.0.

Updating the package node-sass resolved it.

npm i node-sass --save-dev

Failed to compile
./src/styles/index.scss (./node_modules/css-loader/dist/cjs.js??ref--6-oneOf-5-1!./node_modules/postcss-loader/src??postcss!./node_modules/resolve-url-loader??ref--6-oneOf-5-3!./node_modules/sass-loader/lib/loader.js??ref--6-oneOf-5-4!./src/styles/index.scss)
Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (79)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.12.0
This error occurred during the build time and cannot be dismissed.

Answer 51 · 2020-01-08T19:06:56.000Z

npm rebuild node-sass didn't help
helped:
npm uninstall node-sass
npm install node-sass

This is the only thing that worked on MacOS for angular 6 app

Answer 52 · 2020-01-28T17:10:25.000Z

npm update
npm install
npm start

update command updates to latest node-sass version.
Above mentioned steps worked for me.

Answer 53 · 2020-02-20T08:34:07.000Z

npm install -g node-sass

This command saved the day for me

Answer 54 · 2020-04-09T04:12:33.000Z

running npm rebuild node-sass also helps.

this worked fine with me. thanks @rohit-aneja

Answer 55 · 2020-05-14T04:20:05.000Z

if the command "which node-sass" is returning empty, you have to install node-sass
Just run:

npm install node-sass

Still working in May 2020

Answer 56 · 2020-06-02T11:21:36.000Z

For me, I had to update node-sass-chokidar from 1.3.4 to 1.4.0 and the build started working.

Answer 57 · 2022-01-04T22:46:04.000Z

@Titoratus Thank you bro, i've spend one hour on this sh*t. You are a really lifesaver.

Answer 58 · 2022-04-05T16:24:28.000Z

NodeJS Supported node-sass version *
Node 15 5.0+
Node 14 4.14+
Node 13 4.13+, < 5.0
Node 12 4.12+
Node 11 4.10+, < 5.0
Node 10 4.9+
Node 8 4.5.3+, < 5.0
Node < 8 < 5.0 < 57
13

Check file package.json
"node-sass": "^4.14.1",
"preboot": "^4.5.2",
"primeng": "^4.3.0",
"raw-loader": "^0.5.1",
"read-appsettings-json": "^1.0.98",

=> In my situation problem was in the version of node. As I used the newest version 16.6.4 but the version of node-sass was old (4.14.1), I downgraded node to 14.15.5 (nvm install 14.15.5), ran npm install node-sass@4.14.1, rebuilt node npm rebuild node-sass and just then started my app npm start. Worked!

Steps:

1.nvm install 14.15.5 (downgrade node to version that satisfies node-sass)
*https://nodejs.org/en/blog/release/v14.15.5
2.nvm use 14.15.5
3.npm install node-sass@4.14.1 (reinstall node-sass)
4.npm rebuild node-sass
5.npm start

After executing these commands everything is working fine for me.
Chu Xuân Tình