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

node.jsNpmSassGulpGulp Sass

node.js Problem Overview


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.

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

> node-sass@4.14.1 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 node-gyp@3.8.0
gyp info using node@15.0.1 | 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
node-sass@4.14.1 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

node.js Solutions


Solution 1 - node.js

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

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

This command in the console worked for me:

npm rebuild node-sass

Solution 4 - node.js

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

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

Solution 6 - node.js

I ran to the same problem and I found that the best solution is to use gulp-dart-sass. You won't need to downgrade your Node.js(I'm using it with Node version: v15.3.0 right now)

Simple replace gulp-sass to gulp-dart-sass

Solution 7 - node.js

I encountered the same issue after updating my Node.js version from 14.15.5(LTS) to 15.8.0.
In order to resolve this issue I downgraded Node.js version back to 14.15.5(LTS).

I used chocolatey to downgrade NPM. If you don't have chocolatey installed in your system,
you can get Chocolatey from here.

Now to downgrade Node.js we have to do the following steps

  1. Uninstall latest version of the Node.js
    For that you have to use this code.
    choco uninstall nodejs

  2. To install the desired version of Node.js,
    choco install nodejs --version $VersionNumber

in my case,
choco uninstall nodejs
choco install nodejs --version 14.15.5

this solved my issue.

Solution 8 - node.js

Worked for me

  1. npm install with specific node version that you need

    This the version of node that I am using

    npm install -g [email protected] --target_arch=x64

  2. Clean cache

    npm cache clean --force

    rm -rf /node_modules

  3. Install node-sass

    npm install node-sass --save-dev --force

  4. If you have errors and warnings try:

    npm fund

    npm audit fix

    npm install -g [email protected] --target_arch=x64

    npm start

Solution 9 - node.js

I met the same issue, and here's how I was able to fix it:

Firstly, you have to know which node-sass version you are using in your project, then go upgrade or downgrade your current nodeJS version to the compatible version with your current node-sass version, you can know that from this link.

Ofc, stop the server, and close your IDE.

So, the best way to upgrade or downgrade the nodeJS version, has mentioned above in this answer, then remove the node_modules, and package-lock.json and install again.. You can do it as such:

npm cache clean --force

rm -rf /node_modules package-lock.json

npm install

npm audit fix

npm run <your_script_name>

Good Luck!

Solution 10 - node.js

For me, the issue happened after I updated my node version to 16, I downgraded the node version to 14.17.6 and had to uninstall the node-sass version 6 and reinstall node-sass version 4.14 which is compactible with node 14+

npm uninstall node-sass
npm i node-sass@4.14

Solution 11 - node.js

For me the only solution was to downgrade NodeJs from 16(my current version) to 10 version (it can be any version below probably), tried almost all that were advised here and on other websites and only this helped.

Solution 12 - node.js

Here are the steps I followed to make it work.

  • brew uninstall node (Or uninstall with the package manager you used)
  • brew install n
  • sudo chown -R $(whoami) /usr/local/n
  • n 14.15.0

Solution 13 - node.js

For any1 having this problem with SPFx

If you have upgraded your node version, steps to upgrade your SPFx solution

  1. Create a side clean SPFx project (Webpart or Extension (Extension is only with 2019+))

  2. Save somewhere (just in case) the following files package.json, tsconfig.json, package-lock.json

  3. Copy from your new project to your old project only 2 files package.json, tsconfig.json

  4. Run gulp clean

  5. Run npm install

  6. Run gulp build ect.

summerized here

Solution 14 - node.js

I am late to the party but what I did is install nvm and add a small function in .bashrc to change node version as I need using an alias.

function switchNodeVersion()
{
  nvm use 14.6.0
  node-sass [options] <input.scss> [output.css]
  nvm use 16.13.0
}
alias swap=switchNodeVersion

Solution 15 - node.js

  1. In my case I removed node-sass with npm remove node-sass

  2. then I installed node-sass npm i node-sass@next

  3. restarted server

  • Hurray! everything worked fine *

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
QuestionDINA TAKLITView Question on Stackoverflow
Solution 1 - node.jspaulrezmerView Answer on Stackoverflow
Solution 2 - node.jsMelissa HeyingView Answer on Stackoverflow
Solution 3 - node.jsAbdullah AmanView Answer on Stackoverflow
Solution 4 - node.jsAnatolView Answer on Stackoverflow
Solution 5 - node.jsRichard TorcatoView Answer on Stackoverflow
Solution 6 - node.jsClovis RosaView Answer on Stackoverflow
Solution 7 - node.jsAMAL MOHAN NView Answer on Stackoverflow
Solution 8 - node.jsJennifer LedezmaView Answer on Stackoverflow
Solution 9 - node.jsIbrahim BHMBSView Answer on Stackoverflow
Solution 10 - node.jsApPyView Answer on Stackoverflow
Solution 11 - node.jsЕлена ОмView Answer on Stackoverflow
Solution 12 - node.jscrgView Answer on Stackoverflow
Solution 13 - node.jsbresleveloperView Answer on Stackoverflow
Solution 14 - node.jsDragod83View Answer on Stackoverflow
Solution 15 - node.jsRuban DharmarajView Answer on Stackoverflow