Node sass ошибка при установке

I am trying to install node-sass in a project, which perfectly builds and runs on my pc but on my surface I am having major issues when trying to install the packages.

Note: I have tryed reinstalling and rebuilding the project several times.

Summary of the error:

gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Users\Max-T\Documents\Sources\StaffMangerV2\black-dashboard-pro-react-v1.0.0\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Windows_NT 10.0.18362
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Max-T\\Documents\\Sources\\StaffMangerV2\\black-dashboard-pro-react-v1.0.0\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Users\Max-T\Documents\Sources\StaffMangerV2\black-dashboard-pro-react-v1.0.0\node_modules\node-sass
gyp ERR! node -v v12.13.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\react-scripts\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.11.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.11.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Max-T\AppData\Roaming\npm-cache\_logs\2019-10-30T10_05_01_386Z-debug.log

package.json => https://hastebin.com/azetegukes.pl
too much coode so I had to paste it elsewhere.

asked Oct 30, 2019 at 10:14

If anyone runs into this lately… the easiest fix is to replace node-sass with just sass in your dependencies. It’s the more recently maintained version and I only had to change 1 line of code with how it’s initialized and all of my existing code was already compatible.

There are more details at https://sass-lang.com/blog/libsass-is-deprecated under How to migrate.

answered Dec 12, 2021 at 13:25

Matt ToigoMatt Toigo

6591 gold badge6 silver badges6 bronze badges

Don’t use node-sass anymore

node-sass is deprecated. Instead use the new version which is sass.

You can uninstall the old and install the new one with this command

npm uninstall node-sass
npm install sass

answered Aug 10, 2022 at 20:07

AbrahamAbraham

12.4k4 gold badges58 silver badges92 bronze badges

try this command it works for me

sudo npm install -g --unsafe-perm node-sass

answered Apr 28, 2020 at 9:25

After more than 2 hours of trying all sorts of ways (cleaning npm cache, deleting node_modules, trying to install with global switch -g, etc.) to install node-sass and failing every time, I finally changed the mirror to china and it immediately worked for me!! (I know it kinda doesn’t make any sense, considering the error I was getting)

Just for reference, this was the error I was receiving before it finally worked:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.14.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.14.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\****\AppData\Roaming\npm-cache\_logs\2020-06-06T13_56_56_768Z-debug.log

My Node version: v12.18.0
node-sass version in package.json: «^4.14.0»

I changed the mirror as stated in the node-sass npm page.

npm install -g mirror-config-china --registry=http://registry.npm.taobao.org
npm install node-sass

Hope that helps.

answered Jun 6, 2020 at 14:25

SнаđошƒаӽSнаđошƒаӽ

16.8k12 gold badges73 silver badges90 bronze badges

Here are steps fro replacing node-sass with sass which resolved my exact issue:

First remove ‘node-sass’. Go to your package.json (remove it from dependency)
Than, remove package-lock.json file and node_modules
npm install
npm install sass —save

‘npm start’ would be your next step

answered Jul 24 at 22:09

StefaDesignStefaDesign

92910 silver badges19 bronze badges

The best option would probably be to replace node-sass lib with sass one.
But in our case I fixed that by installing nvm and setting local node version to 14.17.6
My node-sass version is 4.14.1

answered Feb 1, 2022 at 10:29

AliakseiAliaksei

1,13611 silver badges21 bronze badges

Источник

I am trying to install node-sass in a project, which perfectly builds and runs on my pc but on my surface I am having major issues when trying to install the packages.

Note: I have tryed reinstalling and rebuilding the project several times.

Summary of the error:

gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Users\Max-T\Documents\Sources\StaffMangerV2\black-dashboard-pro-react-v1.0.0\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:210:5)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Windows_NT 10.0.18362
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Max-T\\Documents\\Sources\\StaffMangerV2\\black-dashboard-pro-react-v1.0.0\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd C:\Users\Max-T\Documents\Sources\StaffMangerV2\black-dashboard-pro-react-v1.0.0\node_modules\node-sass
gyp ERR! node -v v12.13.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\react-scripts\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.9 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.11.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.11.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Max-T\AppData\Roaming\npm-cache\_logs\2019-10-30T10_05_01_386Z-debug.log

package.json => https://hastebin.com/azetegukes.pl
too much coode so I had to paste it elsewhere.

asked Oct 30, 2019 at 10:14

There are more details at https://sass-lang.com/blog/libsass-is-deprecated under How to migrate.

answered Dec 12, 2021 at 13:25

Matt ToigoMatt Toigo

6591 gold badge6 silver badges6 bronze badges

Don’t use node-sass anymore

node-sass is deprecated. Instead use the new version which is sass.

You can uninstall the old and install the new one with this command

npm uninstall node-sass
npm install sass

answered Aug 10, 2022 at 20:07

AbrahamAbraham

12.4k4 gold badges58 silver badges92 bronze badges

try this command it works for me

sudo npm install -g --unsafe-perm node-sass

answered Apr 28, 2020 at 9:25

Just for reference, this was the error I was receiving before it finally worked:

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass@4.14.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass@4.14.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\****\AppData\Roaming\npm-cache\_logs\2020-06-06T13_56_56_768Z-debug.log

My Node version: v12.18.0
node-sass version in package.json: «^4.14.0»

I changed the mirror as stated in the node-sass npm page.

npm install -g mirror-config-china --registry=http://registry.npm.taobao.org
npm install node-sass

Hope that helps.

answered Jun 6, 2020 at 14:25

SнаđошƒаӽSнаđошƒаӽ

16.8k12 gold badges73 silver badges90 bronze badges

Here are steps fro replacing node-sass with sass which resolved my exact issue:

First remove ‘node-sass’. Go to your package.json (remove it from dependency)
Than, remove package-lock.json file and node_modules
npm install
npm install sass —save

‘npm start’ would be your next step

answered Jul 24 at 22:09

StefaDesignStefaDesign

92910 silver badges19 bronze badges

The best option would probably be to replace node-sass lib with sass one.
But in our case I fixed that by installing nvm and setting local node version to 14.17.6
My node-sass version is 4.14.1

answered Feb 1, 2022 at 10:29

AliakseiAliaksei

1,13611 silver badges21 bronze badges

Источник

I’m trying to run a project with npm start and then get the following error in a bunch of different components:

Module build failed: Error: Cannot find module 'node-sass'

Alright, I’m thinking and I run ‘npm install node-sass’, which then leaves me with the following error:

Error: EINVAL: invalid argument, open '/usr/app/client/node_modules/node-sass/package.json'
    at Object.fs.openSync (fs.js:646:18)
    at Object.fs.readFileSync (fs.js:551:33)
    at Object.Module._extensions..json (module.js:670:20)
    at Module.load (module.js:566:32)
    at tryModuleLoad (module.js:506:12)
    at Function.Module._load (module.js:498:3)
    at Module.require (module.js:597:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/usr/app/client/node_modules/node-sass/lib/extensions.js:7:9)
    at Module._compile (module.js:653:30)

I don’t know what it means or what I can do to resolve it, I tried commands like npm rebuild, npm uninstall and then install again, deleted the node_modules folder but that doesn’t seem to do the trick.

Источник

Introduction

Recently I was trying to fix a bug with one of my old projects. So I went to git and did a clone and ran

npm install

The project uses node-sass to complile scss files to CSS and came up with the error:

npm ERR! command failed

A more verbose error looks like the following:

npm ERR! code 1
npm ERR! path D:\myproject\node_modules\gulp-sass\node_modules\node-sass
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node scripts/build.js
npm ERR! Building: C:\Program Files\nodejs\node.exe D:\myproject\node_modules\gulp-sass\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
...
...
npm ERR! gyp info using node-gyp@3.8.0
npm ERR! gyp info using node@17.3.1 | win32 | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb check python checking for Python executable "python2" in the PATH
npm ERR! gyp verb `which` failed Error: not found: python2
npm ERR! gyp verb `which` failed     at getNotFoundError (D:\myproject\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (D:\myproject\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (D:\myproject\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:198:21)
npm ERR! gyp verb `which` failed  python2 Error: not found: python2
npm ERR! gyp verb `which` failed     at getNotFoundError (D:\myproject\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (D:\myproject\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (D:\myproject\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:198:21) {
npm ERR! gyp verb `which` failed   code: 'ENOENT'
npm ERR! gyp verb `which` failed }
npm ERR! gyp verb check python checking for Python executable "python" in the PATH
npm ERR! gyp verb `which` failed Error: not found: python
npm ERR! gyp verb `which` failed     at getNotFoundError (D:\myproject\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (D:\myproject\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (D:\myproject\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:198:21)
npm ERR! gyp verb `which` failed  python Error: not found: python
npm ERR! gyp verb `which` failed     at getNotFoundError (D:\myproject\node_modules\which\which.js:13:12)
npm ERR! gyp verb `which` failed     at F (D:\myproject\node_modules\which\which.js:68:19)
npm ERR! gyp verb `which` failed     at E (D:\myproject\node_modules\which\which.js:80:29)
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\which\which.js:89:16
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\isexe\index.js:42:5
npm ERR! gyp verb `which` failed     at D:\myproject\node_modules\isexe\windows.js:36:5
npm ERR! gyp verb `which` failed     at FSReqCallback.oncomplete (node:fs:198:21) {
npm ERR! gyp verb `which` failed   code: 'ENOENT'
npm ERR! gyp verb `which` failed }
npm ERR! gyp verb could not find "python". checking python launcher
npm ERR! gyp verb could not find "python". guessing location
npm ERR! gyp verb ensuring that file exists: C:\Python27\python.exe
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.
npm ERR! gyp ERR! stack     at PythonFinder.failNoPython (D:\myproject\node_modules\gulp-sass\node_modules\node-gyp\lib\configure.js:484:19)
npm ERR! gyp ERR! stack     at PythonFinder.<anonymous> (D:\myproject\node_modules\gulp-sass\node_modules\node-gyp\lib\configure.js:509:16)
npm ERR! gyp ERR! stack     at D:\myproject\node_modules\graceful-fs\polyfills.js:282:31
npm ERR! gyp ERR! stack     at FSReqCallback.oncomplete (node:fs:198:21)
npm ERR! gyp ERR! System Windows_NT 10.0.19043
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "D:\\,yproject\\node_modules\\gulp-sass\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd D:\myproject\node_modules\gulp-sass\node_modules\node-sass
npm ERR! gyp ERR! node -v v17.3.1
npm ERR! gyp ERR! node-gyp -v v3.8.0
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1

Why is `node-sass` failing to install?

Node-sass is a popular package used in Node.js applications to compile Sass files into CSS.
This means that you can specify the .scss file and get it compiled to css.

The main reason why node-sass would be failing is that its been deprecated and the team behind SASS recommends using Dart SASS or sass for short.

Steps to fix this issue

Updgrade node-sass with sass
Make sure you are using a compatible version of node-sass with Node
Make sure to have installed node-sass and its dependencies on your machine
Clear out the node_modules, package-lock.json and install again
Use the flag --unsafe-perm

Tip: The obvious step is to not use node-sass but sass

1. Updgrade `node-sass` with `sass`

Node-sass has been deprecated and the team behind it recommends using sass.

We just need to remove it as follows:

npm uninstall node-sass --save

Then install sass:

Now if you want to use node-sass for some reason, then follow the next steps.

2. Make sure you are using a compatible version of node-sass with Node

So if you do not want to use the new Dart SASS (sass) and still want to use node-sass, we can change our node version to use a version thats compatible with node-sass

The following table lists the compatible versions of Node with Node-sass:

NodeJS	Supported node-sass version	Node Module
Node 19	8.0+	111
Node 18	8.0+	108
Node 17	7.0+, <8.0	102
Node 16	6.0+	93
Node 15	5.0+, <7.0	88
Node 14	4.14+	83
Node 13	4.13+, <5.0	79
Node 12	4.12+, <8.0	72
Node 11	4.10+, <5.0	67
Node 10	4.9+, <6.0	64
Node 8	4.5.3+, <5.0	57
Node <8	<5.0	<57

One good tool to use to manage Node versions is NVM!

To work with NVM and manage your Node versions we can do the following:

For windows, we can go to the binary and install NVM located here:

https://github.com/coreybutler/nvm-windows/tags

For linux distros we can do the following:

sudo apt install curl 
curl https://raw.githubusercontent.com/creationix/nvm/master/install.sh | bash
source ~/.profile
nvm install node

Uninstall all versions of node with the following command:

nvm uninstall <node version>

Reinstall needed node version:

nvm install <node version>

To get the latest node version we can do nvm install latest

Use node version just installed:

nvm use <node version>

In our case, we can use the command nvm use latest

3. Make sure to have installed node-sass and its dependencies on your machine

node-sass requires a bunch of dependencies and they are required to be installed on your machine first.

In general, make sure that you have installed Python and a build/compiler toolchain. This would vary across systems.

For Unix

Python v3.7, v3.8, v3.9, or v3.10
make
C/C++ compiler toolchain eg GCC

For OSX

Python v3.7, v3.8, v3.9, or v3.10
XCode Command Line Tools which will install clang, clang++, and make.

On Windows

Python v3.7, v3.8, v3.9, or v3.10, head over to the Microsoft Store and download the latest version.
Install the Visual C++ Build Environment. You can do this by either getting the “Visual C++ build tools” workload in Visual Studio Build Tools or by using the “Desktop development with C++” workload in Visual Studio Community.
Open up cmd and type in “npm config set msvs_version 2017”.

Note: If you’re looking to target native ARM64 Node.js on Windows 10 on ARM, make sure to add the components “Visual C++ compilers and libraries for ARM64” and “Visual C++ ATL for ARM64”.

4. Clear out the node_modules, package-lock.json and install again

When previous steps did not work for you, the final option is to nuke everything.

Open up your terminal and go to the project’s root folder:

Delete node_modules folder. This is where all the packages are saved.
Delete the package-lock.json.
Run npm install

Note: Make sure you are running under administrator priveleges.

5. Use the flag `--unsafe-perm`

If you know what you are getting into, then try installing node-sass with the --unsafe-perm flag.

This flag allows npm to run scripts with root privileges.

You can install node-sass with the --unsafe-perm flag by running the following command in your terminal:

npm install node-sass --unsafe-perm

Summary

When working on old projects you may come across NPM install errors with node-sass. The main reason this is the case is because node-sass has been deprecated by the team behind it.

It is recommended to use sass instead. If somehow you still need to use node-sass there are a few things to check to get your project up and running:

check that the version of node-sass is compatible with your version of Node
make sure that you have all the dependencies installed on your machine — eg Python and build/compile tools
clear our your node_modules folder and package-lock.json and run the npm install again
Try using the --unsafe-perm flag if you know what you are doing!

Источник

npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
npm ERR! code 1
npm ERR! path D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-sass
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c C:\Users\Asus\AppData\Local\Temp\postinstall6572545994.cmd
npm ERR! Building: C:\Program Files\nodejs\node.exe D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-gyp\bin\node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library=
npm ERR! gyp info it worked if it ends with ok
npm ERR! gyp verb cli [
npm ERR! gyp verb cli 'C:\\Program Files\\nodejs\\node.exe',
npm ERR! gyp verb cli 'D:\\Web Dev\\Full-Stack Web Development with React Specialization\\Front-End Web UI Frameworks and Tools Bootstrap 4\\week01\\Introduction To Bootstrap\\Bootstrap4\\conFusion\\node_modules\\node-gyp\\bin\\node-gyp.js',
npm ERR! gyp verb cli 'rebuild',
npm ERR! gyp verb cli '--verbose',
npm ERR! gyp verb cli '--libsass_ext=',
npm ERR! gyp verb cli '--libsass_cflags=',
npm ERR! gyp verb cli '--libsass_ldflags=',
npm ERR! gyp verb cli '--libsass_library='
npm ERR! gyp verb cli ]
npm ERR! gyp info using node-gyp@8.4.1
npm ERR! gyp info using node@18.4.0 | win32 | x64
npm ERR! gyp verb command rebuild []
npm ERR! gyp verb command clean []
npm ERR! gyp verb clean removing "build" directory
npm ERR! gyp verb command configure []
npm ERR! gyp verb find Python checking Python explicitly set from command line or npm configuration
npm ERR! gyp verb find Python - "--python=" or "npm config get python" is "C:\Python\Python39\python.exe"
npm ERR! gyp verb find Python - executing "C:\Python\Python39\python.exe" to get executable path
npm ERR! gyp verb find Python - executable path is "C:\Python\Python39\python.exe"
npm ERR! gyp verb find Python - executing "C:\Python\Python39\python.exe" to get version
npm ERR! gyp verb find Python - version is "3.9.7"
npm ERR! gyp info find Python using Python version 3.9.7 found at "C:\Python\Python39\python.exe"
npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 18.4.0
npm ERR! gyp verb command install [ '18.4.0' ]
npm ERR! gyp verb install input version string "18.4.0"
npm ERR! gyp verb install installing version: 18.4.0
npm ERR! gyp verb install --ensure was passed, so won't reinstall if already installed
npm ERR! gyp verb install version is already installed, need to check "installVersion"
npm ERR! gyp verb got "installVersion" 9
npm ERR! gyp verb needs "installVersion" 9
npm ERR! gyp verb install version is good
npm ERR! gyp verb get node dir target node version installed: 18.4.0
npm ERR! gyp verb build dir attempting to create "build" dir: D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-sass\build
npm ERR! gyp verb build dir "build" dir needed to be created? Yes
npm ERR! gyp verb find VS msvs_version was set from command line or npm config
npm ERR! gyp verb find VS - looking for Visual Studio version 2017
npm ERR! gyp verb find VS VCINSTALLDIR not set, not running in VS Command Prompt
npm ERR! gyp verb find VS could not use PowerShell to find Visual Studio 2017 or newer, try re-running with '--loglevel silly' for more details
npm ERR! gyp verb find VS looking for Visual Studio 2015
npm ERR! gyp verb find VS - not found
npm ERR! gyp verb find VS not looking for VS2013 as it is only supported up to Node.js 8
npm ERR! gyp ERR! find VS
npm ERR! gyp ERR! find VS msvs_version was set from command line or npm config
npm ERR! gyp ERR! find VS - looking for Visual Studio version 2017
npm ERR! gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
npm ERR! gyp ERR! find VS could not use PowerShell to find Visual Studio 2017 or newer, try re-running with '--loglevel silly' for more details
npm ERR! gyp ERR! find VS looking for Visual Studio 2015
npm ERR! gyp ERR! find VS - not found
npm ERR! gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
npm ERR! gyp ERR! find VS
npm ERR! gyp ERR! find VS valid versions for msvs_version:
npm ERR! gyp ERR! find VS
npm ERR! gyp ERR! find VS **************************************************************
npm ERR! gyp ERR! find VS You need to install the latest version of Visual Studio
npm ERR! gyp ERR! find VS including the "Desktop development with C++" workload.
npm ERR! gyp ERR! find VS For more information consult the documentation at:
npm ERR! gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
npm ERR! gyp ERR! find VS **************************************************************
npm ERR! gyp ERR! find VS
npm ERR! gyp ERR! configure error
npm ERR! gyp ERR! stack Error: Could not find any Visual Studio installation to use
npm ERR! gyp ERR! stack at VisualStudioFinder.fail (D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-gyp\lib\find-visualstudio.js:122:47)
npm ERR! gyp ERR! stack at D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-gyp\lib\find-visualstudio.js:75:16
npm ERR! gyp ERR! stack at VisualStudioFinder.findVisualStudio2013 (D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-gyp\lib\find-visualstudio.js:363:14)
npm ERR! gyp ERR! stack at D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-gyp\lib\find-visualstudio.js:71:14
npm ERR! gyp ERR! stack at D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-gyp\lib\find-visualstudio.js:384:16
npm ERR! gyp ERR! stack at D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-gyp\lib\util.js:54:7
npm ERR! gyp ERR! stack at D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-gyp\lib\util.js:33:16
npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:397:5)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:537:28)
npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1091:16)
npm ERR! gyp ERR! System Windows_NT 10.0.19044
npm ERR! gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "D:\\Web Dev\\Full-Stack Web Development with React Specialization\\Front-End Web UI Frameworks and Tools Bootstrap 4\\week01\\Introduction To Bootstrap\\Bootstrap4\\conFusion\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
npm ERR! gyp ERR! cwd D:\Web Dev\Full-Stack Web Development with React Specialization\Front-End Web UI Frameworks and Tools Bootstrap 4\week01\Introduction To Bootstrap\Bootstrap4\conFusion\node_modules\node-sass
npm ERR! gyp ERR! node -v v18.4.0
npm ERR! gyp ERR! node-gyp -v v8.4.1
npm ERR! gyp ERR! not ok
npm ERR! Build failed with error code: 1

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Asus\AppData\Local\npm-cache\_logs\2022-07-06T16_35_57_546Z-debug-0.log

Not applicable.

Источник

Don’t use node-sass anymore

Don’t use node-sass anymore

Introduction

Why is `node-sass` failing to install?

Steps to fix this issue

Tip: The obvious step is to not use `node-sass` but `sass`

1. Updgrade `node-sass` with `sass`

2. Make sure you are using a compatible version of node-sass with Node

3. Make sure to have installed node-sass and its dependencies on your machine

For Unix

For OSX

On Windows

4. Clear out the node_modules, package-lock.json and install again

5. Use the flag `--unsafe-perm`

Summary

Интересное по теме:

Don’t use node-sass anymore

Don’t use node-sass anymore

Introduction

Why is node-sass failing to install?

Steps to fix this issue

Tip: The obvious step is to not use node-sass but sass

1. Updgrade node-sass with sass

2. Make sure you are using a compatible version of node-sass with Node

3. Make sure to have installed node-sass and its dependencies on your machine

For Unix

For OSX

On Windows

4. Clear out the node_modules, package-lock.json and install again

5. Use the flag --unsafe-perm

Summary

Интересное по теме:

Why is `node-sass` failing to install?

Tip: The obvious step is to not use `node-sass` but `sass`

1. Updgrade `node-sass` with `sass`

5. Use the flag `--unsafe-perm`