Abdelbasset Belaid
Abdelbasset Belaid

Reputation: 139

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

this what VSC terminal show me

Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (93)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.14.1

i tried some solutions in stack overflow:

npm rebuild node-sass

and

npm uninstall node-sass && npm install node-sass

but does't work with , i saw some people talk about node version if support sass or not, im using v16.14.0 it's LTS version should that support i guess, i hope someone can help and THANK YOU

Upvotes: 7

Views: 11335

Answers (4)

Mbay
Mbay

Reputation: 75

I was updated my nodejs version 18.18 then this error occured to me. I'm using webpack with the version of 5 and node-sass with the version of 7. But I had no sass module.

The solution for me was installing the sass.

npm i sass --save-dev

Upvotes: 0

xhafan
xhafan

Reputation: 2416

I fixed this issue by forcing Visual Studio to use the node version I installed instead of VS installed version of node:

Go to Visual Studio, Tools -> Options, Project and Solutions -> Web Package Management -> External Web Tools, and move the $(PATH) to the second place below .\node_modules\.bin and above $(VSInstalledExternalTools). Restart Visual Studio.

Found this solution here.

Upvotes: 2

Jorj
Jorj

Reputation: 2701

Fix the errors due to node-sass:

 1. Remove "sass" and "sass-loader" from package.json
 2. rm -rf node_modules
 3. npm install
 4. npm install sass --save-dev
 5. npm install sass-loader --save-dev

The versions of some packages is enforced in package.json. The solution is to re-add them by letting npm to establish their right version for your OS.

Upvotes: 0

Matt Hatcher
Matt Hatcher

Reputation: 760

It's almost like it's trying to install the 4.x branch which only supports up to Node 14.

Try installing the 7.0.1 (current latest).

npm i [email protected]

I'd recommend going ahead and wiping node_modules prior to installing just to be safe.

If that doesn't work, can you please post the entire output in the comment?

Upvotes: 3

Related Questions