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

Question

I have tried to install gulp-sass latest version with npm i gulp-sass --save-dev in the begining I got a lot of errors but later solved them. But whenever I try to run gulp I got this error:

Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (88)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.14.1
    at module.exports (C:\Users\user\Desktop\HPortf\node_modules\node-sass\lib\binding.js:13:13)
    at Object.<anonymous> (C:\Users\user\Desktop\HPortf\node_modules\node-sass\lib\index.js:14:35)
    at Module._compile (node:internal/modules/cjs/loader:1083:30)
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1112:10)
    at Module.load (node:internal/modules/cjs/loader:948:32)
    at Function.Module._load (node:internal/modules/cjs/loader:789:14)
    at Module.require (node:internal/modules/cjs/loader:972:19)
    at require (node:internal/modules/cjs/helpers:88:18)
    at Object.<anonymous> (C:\Users\user\Desktop\HPortf\node_modules\gulp-sass\index.js:166:21)
    at Module._compile (node:internal/modules/cjs/loader:1083:30)

I have tried to fix the problem with npm rebuild node-sass --force but it rise error too.

PS C:\Users\user\Desktop\HPortf> npm rebuild node-sass --force
npm WARN using --force I sure hope you know what you are doing.

> [email protected] install C:\Users\user\Desktop\HPortf\node_modules\node-sass
> node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v4.14.1/win32-x64-88_binding.node
Cannot download "https://github.com/sass/node-sass/releases/download/v4.14.1/win32-x64-88_binding.node":

HTTP error 404 Not Found

Hint: If github.com is not accessible in your location
      try setting a proxy via HTTP_PROXY, e.g.

      export HTTP_PROXY=http://example.com:1234

or configure npm proxy via

      npm config set proxy http://example.com:8080

> [email protected] postinstall C:\Users\user\Desktop\HPortf\node_modules\node-sass
> node scripts/build.js

Building: C:\Program Files\nodejs\node.exe C:\Users\user\Desktop\HPortf\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
gyp info it worked if it ends with ok
gyp verb cli [
gyp verb cli   'C:\\Program Files\\nodejs\\node.exe',
gyp verb cli   'C:\\Users\\user\\Desktop\\HPortf\\node_modules\\node-gyp\\bin\\node-gyp.js',
gyp verb cli   'rebuild',
gyp verb cli   '--verbose',
gyp verb cli   '--libsass_ext=',
gyp verb cli   '--libsass_cflags=',
gyp verb cli   '--libsass_ldflags=',
gyp verb cli   '--libsass_library='
gyp verb cli ]
gyp info using [email protected]
gyp info using [email protected] | win32 | x64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb check python checking for Python executable "python2" in the PATH
gyp verb `which` failed Error: not found: python2
gyp verb `which` failed     at getNotFoundError (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:183:21)
gyp verb `which` failed  python2 Error: not found: python2
gyp verb `which` failed     at getNotFoundError (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:183:21) {
gyp verb `which` failed   code: 'ENOENT'
gyp verb `which` failed }
gyp verb check python checking for Python executable "python" in the PATH
gyp verb `which` failed Error: not found: python
gyp verb `which` failed     at getNotFoundError (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:183:21)
gyp verb `which` failed  python Error: not found: python
gyp verb `which` failed     at getNotFoundError (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:13:12)
gyp verb `which` failed     at F (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:68:19)
gyp verb `which` failed     at E (C:\Users\user\Desktop\HPortf\node_modules\which\which.js:80:29)
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\which\which.js:89:16
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\isexe\index.js:42:5
gyp verb `which` failed     at C:\Users\user\Desktop\HPortf\node_modules\isexe\windows.js:36:5
gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:183:21) {
gyp verb `which` failed   code: 'ENOENT'
gyp verb `which` failed }
gyp verb could not find "python". checking python launcher
gyp verb could not find "python". guessing location
gyp verb ensuring that file exists: C:\Python27\python.exe
gyp ERR! configure error
gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
gyp ERR! stack     at PythonFinder.failNoPython (C:\Users\user\Desktop\HPortf\node_modules\node-gyp\lib\configure.js:484:19)gyp ERR! stack     at PythonFinder.<anonymous> (C:\Users\user\Desktop\HPortf\node_modules\node-gyp\lib\configure.js:509:16) 
gyp ERR! stack     at callback (C:\Users\user\Desktop\HPortf\node_modules\graceful-fs\polyfills.js:295:20)
gyp ERR! stack     at FSReqCallback.oncomplete (node:fs:183:21)
gyp ERR! System Windows_NT 10.0.18362
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\user\\Desktop\\HPortf\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Users\user\Desktop\HPortf\node_modules\node-sass
gyp ERR! node -v v15.0.1
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
[email protected] C:\Users\user\Desktop\HPortf\node_modules\node-sass
PS C:\Users\user\Desktop\HPortf>

• node and npm version

$ node --version
v15.0.1
user (master *) HmdPort
$ npm --version
6.14.8

Solution 1

Thanks to jonrsharpe.

Worked for me:

1. install / downgrade node.js to a stable version (LTS) like 14.15.0
2. install the compatible node-sass version via npm install [email protected]; you can find the list here, or even install gulp-sasswith npm i gulp-sass --save-dev.

direct link to list

Solution 2

None of the above worked for me. So, instead I uninstalled node-sass and installed just sass. No more errors!

npm uninstall node-sass

npm i sass

Solution 3

This command in the console worked for me:

npm rebuild node-sass

Solution 4

Warning: LibSass and Node Sass are deprecated. While they will continue to receive maintenance releases indefinitely, there are no plans to add additional features or compatibility with any new CSS or Sass features. Projects that still use it should move onto Dart Sass.

the node-sass package is deprecated.

Instead install sass instead like this:

yarn add sass -D
# or
npm i sass --save-dev

Solution 5

remove node-sass

npm remove node-sass

then install

npm i node-sass@npm:sass -D

Node sass project is deprecated. Don't use it anymore!

https://sass-lang.com/blog/libsass-is-deprecated

The new project uses Dart. https://sass-lang.com/dart-sass

View more solutions

Comments

[jonrsharpe]

So did you go to github.com/sass/node-sass/releases/tag/v4.14.1? That hasn't been built for Node 15, you'll have to downgrade Node until v5 gets released.

[DINA TAKLIT]

you mean I should install a version less than node 15?

[jonrsharpe]

Yes, exactly. Unless you really need some specific feature I'd generally recommend using the active LTS version (listed on the home page as "Recommended For Most Users"), currently v14.

[DINA TAKLIT]

I got you I installed current version of node I need to install LTS version, I will try and see.

[DINA TAKLIT]

Thank you @jonrsharpe it was a node version problem I have donwload stable version and I have delete node_module and reinstall things and worked well, you can post and answer so others take advantages of it, again thank you so much for paying my attention to it.

[Andreas]

the node-sass project itself states, that it is deprecated and recommends to move to dart-sass. In the context of Gulp the answer of @ClovisRosa manages it gracefully.

[DINA TAKLIT]

Yes the problem was with current version of node that has some bugs, so installing LTS version will fix the issues than you can install gulp sass without installing node-sass without precising a version coz the latest one is compatibel with LTS node version :)

[DINA TAKLIT]

Sometimes the non stable version create many problems. Even if u can manage this problem with this command u may face other problems, you will spend ur life fixing errors! this is bad. So it is alwyas better to install a stable version.

[DINA TAKLIT]

But in my case I have tried to install gulp-sass where the error rised up. Maybe gulp-sass is dependent in node-sass yet

[stevec]

Current node version 15.X does not supported by some node-modules. Had to spend much time to review each node-module and decided to downgrade node version. thanks for your posting.

[karfus]

Worked for me...Cypress React component testing (github.com/cypress-io/cypress/tree/develop/npm/react) failed to load (with the error indicated in the OP question) otherwise. Thanks!

[Code-Apprentice]

In the link you give to the node-sass entry on npm, what is the difference between "NodeJS" and "Node Module". How do I install a specific version of "Node Module"?

[Andreas]

This is actually a super solution, as the node-sass project itself is deprecated now and recommends to move to dart-sass officially.

[crg]

Does not work on MAC M1. Nothing works on MAC M1 :')

[silvalli]

wfm after my edit to crg’s answer – macOS 10.15.7 (if that matters)

[Janne]

This seems to work for me as well. My Vue2 environment failed to start with "npm run watch" after I upgraded npm & node so that I could start building Vue3 projects. Removing node-sass on Vue2 project and replacing it with sass fixed running watch/serve

[Moongazer]

Its end of 2021 and the error still exists even for the Node LTS version 16! Precisely: "Unsupported runtime (102)". Also, node-sass v6.0.1 doc says it is compatible with v16 on Linux

[Sivu]

This solution worked for me on MacBook Pro (Big Sur) 64-bit

[ryanlee]

yes, I had installed the latest node version v17.x， and this problem solved only when I change my node version to 14. on mac you can use brew install node@14

[am0wa]

14.15.1 has worked also.

[Ousmane]

Plus sass is now the recommanded package since LibSass and Node Sass are deprecated 😮.