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
asked Jun 27, 2022 at 21:14
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 node-sass@7.0.1
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?
answered Jun 27, 2022 at 21:23
Matt HatcherMatt Hatcher
6331 gold badge4 silver badges17 bronze badges
10
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.
answered Nov 3, 2022 at 14:42
JorjJorj
2,3361 gold badge18 silver badges12 bronze badges
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.
answered Jan 31 at 9:15
xhafanxhafan
2,05224 silver badges25 bronze badges
При сборке проекта ошибка:
Module build failed: Error: Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (64)
node -v
v10.10.0
npm -v
6.4.1
npm ls node-sass
├─┬ laravel-mix@1.7.2
│ └── node-sass@4.13.1
└── node-sass@4.13.1
уже делал:
кеш чистил, node_modules удалял, npm rebuild node-sass делал, версию node менял
Что еще сделать?
-
Вопрос заданболее трёх лет назад
-
24215 просмотров
Мне помогла пересборка модуля:
npm rebuild node-sass
Удалить node_modules и package-lock и установите зависимости
Долго мучился с этой проблемой, никакой npm rebuild node-sass не помогал — тоже выдавал какие-то ошибки.
Почитал повнимательнее — оказалось, что он волне внятно пишет: ошибка gcc, не поддерживаемый ключ командной строки -std=c++14′ . Опаньки, оказывается, ему нужен более свежий gcc (g++), чем установлен у меня в системе (Centos 7). Обновил gcc до 7.3.1 и всё заработало — rebuild прошёл без ошибок, node-sass скомпилировался и заработал.
Надеюсь, это поможет нубам вроде меня сэкономить время и нервы ))
Пригласить эксперта
ничего из вышеперечисленного не решает вопрос, помогла установка nodejs версии в соответствии с https://www.npmjs.com/package/node-sass, здесь указано какой версии должен быть nodejs в зависимости от того, какая node-sass версия у вас.
Гляньте сюда. С такой проблемой уже обращались в issues
Если у вас установлен sass-loader попробуйте его обновить npm update sass-loader, мне помогло
Мне помогла переустановка этого модуля.
npm remove node-sass
npm install node-sass
В моем случае ни пересборка node-sass не помогала, ни реинстал всего с удалением package-local.json и node_modules.
Я использую Vue cli для работы над готовым проектом под Ubuntu.
Вот какой список действий следует предпринять:
— удалите node_modules;
— удалите package-lock.json;
— в package.json удалите node-sass;
— разинстальте все через npm i;
— после npm i пропишите npm i sass.
По факту мы меняем node-sass на sass которые могут собирать ваш исходный код sass/scss и начнет все работать. Удачи и надеюсь кому-то пригодится.
Мне помогло прочитать документацию:
Плагин Sass для Gulp. Прежде чем сообщать о проблеме, убедитесь, что вы обновили gulp-sass до последней версии и ознакомились с нашим разделом «Распространенные проблемы и их исправления». Перенос существующего проекта на версию 5? Пожалуйста, прочтите наше (краткое!) руководство по миграции.
Изменил :
— const sass = require(‘gulp-sass’));
— const compiler = require(‘sass’);
— sass.compiler = compiler;
+ const sass = require(‘gulp-sass’)(require(‘sass’));
Запустил:
npm install sass gulp-sass —save-dev
-
Показать ещё
Загружается…
05 февр. 2023, в 02:41
3000 руб./за проект
05 февр. 2023, в 01:37
2000 руб./за проект
05 февр. 2023, в 01:09
20000 руб./за проект
Минуточку внимания
- Table of contents
- Error: Node Sass does not yet support your current environment
Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (88)
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.
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:UsersuserDesktopHPortfnode_modulesnode-sasslibbinding.js:13:13) at Object.<anonymous> (C:UsersuserDesktopHPortfnode_modulesnode-sasslibindex.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:UsersuserDesktopHPortfnode_modulesgulp-sassindex.js:166:21) at Module._compile (node:internal/modules/cjs/loader:1083:30)
PS C:UsersuserDesktopHPortf> npm rebuild node-sass --force npm WARN using --force I sure hope you know what you are doing. > [email protected] install C:UsersuserDesktopHPortfnode_modulesnode-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:UsersuserDesktopHPortfnode_modulesnode-sass > node scripts/build.js Building: C:Program Filesnodejsnode.exe C:UsersuserDesktopHPortfnode_modulesnode-gypbinnode-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:UsersuserDesktopHPortfnode_moduleswhichwhich.js:13:12) gyp verb `which` failed at F (C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:68:19) gyp verb `which` failed at E (C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:80:29) gyp verb `which` failed at C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:89:16 gyp verb `which` failed at C:UsersuserDesktopHPortfnode_modulesisexeindex.js:42:5 gyp verb `which` failed at C:UsersuserDesktopHPortfnode_modulesisexewindows.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:UsersuserDesktopHPortfnode_moduleswhichwhich.js:13:12) gyp verb `which` failed at F (C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:68:19) gyp verb `which` failed at E (C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:80:29) gyp verb `which` failed at C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:89:16 gyp verb `which` failed at C:UsersuserDesktopHPortfnode_modulesisexeindex.js:42:5 gyp verb `which` failed at C:UsersuserDesktopHPortfnode_modulesisexewindows.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:UsersuserDesktopHPortfnode_moduleswhichwhich.js:13:12) gyp verb `which` failed at F (C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:68:19) gyp verb `which` failed at E (C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:80:29) gyp verb `which` failed at C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:89:16 gyp verb `which` failed at C:UsersuserDesktopHPortfnode_modulesisexeindex.js:42:5 gyp verb `which` failed at C:UsersuserDesktopHPortfnode_modulesisexewindows.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:UsersuserDesktopHPortfnode_moduleswhichwhich.js:13:12) gyp verb `which` failed at F (C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:68:19) gyp verb `which` failed at E (C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:80:29) gyp verb `which` failed at C:UsersuserDesktopHPortfnode_moduleswhichwhich.js:89:16 gyp verb `which` failed at C:UsersuserDesktopHPortfnode_modulesisexeindex.js:42:5 gyp verb `which` failed at C:UsersuserDesktopHPortfnode_modulesisexewindows.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:Python27python.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:UsersuserDesktopHPortfnode_modulesnode-gyplibconfigure.js:484:19)gyp ERR! stack at PythonFinder.<anonymous> (C:UsersuserDesktopHPortfnode_modulesnode-gyplibconfigure.js:509:16) gyp ERR! stack at callback (C:UsersuserDesktopHPortfnode_modulesgraceful-fspolyfills.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:UsersuserDesktopHPortfnode_modulesnode-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:UsersuserDesktopHPortfnode_modulesnode-sass PS C:UsersuserDesktopHPortf>
$ node --version v15.0.1 user (master *) HmdPort $ npm --version 6.14.8
npm uninstall node-sass
npm i sass
npm rebuild node-sass
yarn add sass -D # or npm i sass --save-dev
npm remove node-sass
npm i [email protected]:sass -D
npm uninstall node-sass npm i [email protected]
function switchNodeVersion() { nvm use 14.6.0 node-sass [options] <input.scss> [output.css] nvm use 16.13.0 } alias swap=switchNodeVersion
{ "name": "myproject", "version": "1.0.0", "private": true, "engines": { "node": "16.x" }, "dependencies": {....
Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (93)
gulp-sass 4.1.0 uses node-sass 4, and node-sass 4 does not support Node.js 16, as indicated in this table. To support Node.js 16, upgrade gulp-sass: the latest version …
"scripts": { "start": "gulp watch" }, "dependencies": { "@fortawesome/fontawesome-free": "5.15.1", "@ttskch/select2-bootstrap4-theme": "^1.5.2", "bootstrap": "4.5.3", "bootstrap-datepicker": "^1.9.0", "jquery": "3.5.1", "jquery.easing": "^1.4.1", "select2": "^4.1.0-rc.0", "gulp": "4.0.2" }, "devDependencies": { "browser-sync": "2.26.13", "del": "6.0.0", "gulp": "4.0.2", "gulp-autoprefixer": "7.0.1", "gulp-clean-css": "4.3.0", "gulp-header": "2.0.9", "gulp-plumber": "^1.2.1", "gulp-rename": "2.0.0", "gulp-sass": "4.1.0", "gulp-uglify": "3.0.2", "merge-stream": "2.0.0" }
npm install -D [email protected]
Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (93)
Even using command npm rebuild node-sass is not changing anything.. Answer. gulp-sass 4.1.0 uses node-sass 4, and node-sass 4 does not support Node.js 16, as indicated in this …
"scripts": { "start": "gulp watch" }, "dependencies": { "@fortawesome/fontawesome-free": "5.15.1", "@ttskch/select2-bootstrap4-theme": "^1.5.2", "bootstrap": "4.5.3", "bootstrap-datepicker": "^1.9.0", "jquery": "3.5.1", "jquery.easing": "^1.4.1", "select2": "^4.1.0-rc.0", "gulp": "4.0.2" }, "devDependencies": { "browser-sync": "2.26.13", "del": "6.0.0", "gulp": "4.0.2", "gulp-autoprefixer": "7.0.1", "gulp-clean-css": "4.3.0", "gulp-header": "2.0.9", "gulp-plumber": "^1.2.1", "gulp-rename": "2.0.0", "gulp-sass": "4.1.0", "gulp-uglify": "3.0.2", "merge-stream": "2.0.0" }
npm install -D [email protected]
Error: Node Sass does not yet support your current environment
Then you would wanna use sass package instead of node-sass, as it’s deprecated. And for that run those commands: npm uninstall node-sass —save npm install …
./src/style/base.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/dist/cjs.js??ref--6-oneOf-5-4!./src/style/base.scss) Error: Node Sass does not yet support your current environment: Linux 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
[[email protected]]~/Documents/GitHub/react-admin% nvm list v8.17.0 v10.24.1 -> v16.13.0 v17.2.0 system default -> 8 (-> v8.17.0)
{ "name": "react-admin", "version": "0.1.0", "private": true, "dependencies": { "@ant-design/compatible": "1.0.8", "animate.css": "^3.7.2", "antd": "^4.0.0", "axios": "^0.19.0", "braft-editor": "^2.3.8", "echarts": "^4.4.0", "is-core-module": "2.2.0", "moment": "2.29.1", "nprogress": "^0.2.0", "react": "^17.0.2", "react-dom": "^17.0.2", "react-highlight-words": "0.17.0", "react-loadable": "^5.5.0", "react-redux": "^7.1.1", "react-router-dom": "^5.1.1", "react-scripts": "^3.2.0", "redux": "^4.0.4", "redux-logger": "3.0.6", "redux-promise-middleware": "^6.1.2", "redux-thunk": "^2.3.0", "screenfull": "^5.0.0" }, "scripts": { "start": "react-app-rewired start", "build": "CI=false && react-app-rewired build", "test": "react-app-rewired test", "eject": "react-scripts eject" }, "eslintConfig": { "extends": "react-app" }, "browserslist": { "production": [ ">0.2%", "not dead", "not op_mini all" ], "development": [ "last 1 chrome version", "last 1 firefox version", "last 1 safari version" ] }, "husky": { "hooks": { "pre-commit": "lint-staged" } }, "lint-staged": { "src/**/*.{js,jsx,ts,tsx,json,css,scss,md}": [ "node_modules/.bin/prettier --write", "git add" ], "src/**/*.{css,scss,less,json,html,md,markdown}": [ "node_modules/.bin/prettier --write", "git add" ] }, "devDependencies": { "@babel/helper-builder-react-jsx": "^7.12.13", "babel-plugin-import": "^1.12.2", "customize-cra": "^0.8.0", "husky": "^3.0.9", "lint-staged": "^9.4.2", "sass": "1.37.0", "prettier": "^1.18.2", "react-app-rewired": "^2.1.4" } }
npm install -g n n stable # if one of the commands does not pass, you may need to use sudo sudo npm install -g n sudo n stable
npm uninstall node-sass --save npm install sass --save
npm install -g n n 14 # if one of the commands does not pass, you may need to use sudo sudo npm install -g n sudo n 14
Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (88)
Thanks to jonrsharpe. Worked for me: install / downgrade node.js to a stable version (LTS) like 14.15.0; install the compatible node-sass version via npm install [email protected]; you can …
yarn add sass -D # or npm i sass --save-dev
Answers for «node sass does not yet support your current environment windows 64-bit with unsupported runtime»
npm update node-sass. Answers for «node sass does not yet support your current environment windows 64-bit with unsupported runtime»
npm update node-sass
npm rebuild node-sass
npm install --save-dev node-sass
Next Lesson PHP Tutorial
#node.js #sass #gulp
Вопрос:
Я пытаюсь запустить свою веб-часть SPFx локально с помощью gulp serve
команды, но я получаю эту ошибку:-
D:spfx-MyModalPopupgt;code . D:spfx-MyModalPopupgt;gulp serve 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 at module.exports (D:spfx-MyModalPopupnode_modulesnode-sasslibbinding.js:13:13) at Object.lt;anonymousgt; (D:spfx-MyModalPopupnode_modulesnode-sasslibindex.js:14:35) at Module._compile (node:internal/modules/cjs/loader:1101:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10) at Module.load (node:internal/modules/cjs/loader:981:32) at Function.Module._load (node:internal/modules/cjs/loader:822:12) at Module.require (node:internal/modules/cjs/loader:1005:19) at require (node:internal/modules/cjs/helpers:102:18) at Object.lt;anonymousgt; (D:spfx-MyModalPopupnode_modules@microsoftgulp-core-build-sasslibSassTask.js:12:18) at Module._compile (node:internal/modules/cjs/loader:1101:14)
Running into errors while developing a project is a significant hassle, and nothing is more annoying than fixing errors in your build pipeline. These errors creep in over time, whether you’re using gulp, webpack, grunt, or anything else. Below we will look at how to fix the Node Sass unsupported runtime error.
The Problem
You go to run the build pipeline for your project, and suddenly, you see this error.
Error: Node Sass does not yet support your current environment: Linux 64-bit with Unsupported runtime (83)
Everything worked fine before, so what changed, and why do we see this error?
The error above means that your currently installed Node version and the version of the node-sass package in your node_modules folder are mismatched and not compatible. At some point, you may have updated your Node version, and now some of your installed packages may not jive.
The Solution
The solution here is simple. Run the following command:
npm rebuild node-sass
This command will recompile all your node-sass plugins with the new Node binary.
This command may take some time, so let it run, and node-sass should be fixed.
Alternatively, you can remove node-sass entirely and reinstall it with the following command:
npm uninstall node-sass && npm install node-sass
Lastly, you can delete your entire node_modules folder and run npm install to reinstall it all again.
Follow Up
Remember, if you are going to be upgrading your Node version in your development environment, it’s always a good idea to use a package such as NVM to maintain proper version control. NVM will allow you to install and then switch between different Node versions easily. You always want to keep your development environment mirrored as closely as possible to your production environment. At the same time, you want the ability to try out new Node versions to take advantage of newly added features.
Another approach to fix the “Node Sass does not yet support your current environment” error would be to downgrade your Node back to the version it was when node-sass worked. You could use the nvm use [node version] command to achieve this.
Getting below error after installed latest node.js (v16.13.1)
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 have created static pages for my application and use sass and gulp
I have a static pages and using Sass in the page and use gulp to run on the browser.(npm install). Below are the version which worked my application:
- Node.js — 12.18.0
- gulp — «4.0.2»
- «gulp-sass»: «4.1.0»
Package.json file
"scripts": {
"start": "gulp watch"
},
"dependencies": {
"@fortawesome/fontawesome-free": "5.15.1",
"@ttskch/select2-bootstrap4-theme": "^1.5.2",
"bootstrap": "4.5.3",
"bootstrap-datepicker": "^1.9.0",
"jquery": "3.5.1",
"jquery.easing": "^1.4.1",
"select2": "^4.1.0-rc.0",
"gulp": "4.0.2"
},
"devDependencies": {
"browser-sync": "2.26.13",
"del": "6.0.0",
"gulp": "4.0.2",
"gulp-autoprefixer": "7.0.1",
"gulp-clean-css": "4.3.0",
"gulp-header": "2.0.9",
"gulp-plumber": "^1.2.1",
"gulp-rename": "2.0.0",
"gulp-sass": "4.1.0",
"gulp-uglify": "3.0.2",
"merge-stream": "2.0.0"
}
Even using command npm rebuild node-sass
is not changing anything.
17/03/2021
by Gav
If you ever update your version of node then you might start running into the “Node Sass does not yet support your current environment” error. I’ve had this happen a few times (including today), and thought that it might be nice to put a fix here for anyone who might be looking.
This problem happens because the version of node-sass that you have installed is no longer compatible with the version of node you are trying to run it with. I guess this could work either way, but it is more likely that your node-sass version is behind; which is nice, because I would rather upgrade an npm package than downgrade node.
Here are a couple of things you could try. Don’t worry, they are nice and quick, with little fuss.
Note: If you have installed node-sass globally then you will need to run with a ‘-g’ flag.
Rebuild node-sass
npm rebuild node-sass
or
npm rebuild -g node-sass
Running rebuild basically recompiles the package to match the new node version. However, if this doesn’t work for you (which it doesn’t for me) then your best bet is to uninstall and reinstall node-sass.
Uninstall and re-install node-sass
npm uninstall node-sass && npm install node-sass
or
npm uninstall -g node-sass && npm install -g node-sass
Yup, that’s right. If it doesn’t work, wipe it clean and start again!