Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

npm ERR (node-sass: Command failed) after executing npm i

See original GitHub issue

Browser type and version: Microsoft Edge Version 92.0.902.84 (Official build) (64-bit)
Terminal type: cmd.exe
Node version: v16.8.0
NPM version: 7.21.1
node-sass version: 6.0.1
OS type and version: Microsoft Windows (Version: 21H1 - OS build: 19043.1165)
Describe the bug Following the guide from README.md, after executing npm i, these npm ERRs were thrown, the issue seems to be not able to install node-sass to the current folder:
To Reproduce (on WINDOWS) Steps to reproduce the behavior:

clone repo from https://github.com/mike-works/sass-fundamentals.git
cd sass-fundamentals
Run npm i
See error: npm WARN deprecated set-value@2.0.0: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm WARN deprecated mixin-deep@1.3.1: Critical bug fixed in v2.0.1, please upgrade to the latest version. npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated har-validator@5.0.3: this library is no longer supported npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated debug@4.0.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.0.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.0.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.0.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated travis-deploy-once@5.0.11: We recommend to use Travis Build Stages instead npm WARN deprecated @babel/polyfill @7.0.0: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information. npm WARN deprecated request@2.87.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated uuid@3.3.2: 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 mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated tar@2.2.1: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated core-js@2.5.7: core-js@❤️.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. npm ERR! code 1 npm ERR! path D:\Self-Guided\HTML-CSS\sass-fundamentals\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:\Self-Guided\HTML-CSS\sass-fundamentals\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:\Self-Guided\HTML-CSS\sass-fundamentals\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@3.8.0 npm ERR! gyp info using node@16.8.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 check python checking for Python executable “C:\Users\ASUS.windows-build-tools\python27\python.exe” in the PATH npm ERR! gyp verb which succeeded C:\Users\ASUS.windows-build-tools\python27\python.exe C:\Users\ASUS.windows-build-tools\python27\python.exe npm ERR! gyp verb check python version C:\Users\ASUS\.windows-build-tools\python27\python.exe -c "import sys; print "2.7.15 npm ERR! gyp verb check python version .%s.%s" % sys.version_info[:3];" returned: %j npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 16.8.0 npm ERR! gyp verb command install [ ‘16.8.0’ ] npm ERR! gyp verb install input version string “16.8.0” npm ERR! gyp verb install installing version: 16.8.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: 16.8.0 npm ERR! gyp verb build dir attempting to create “build” dir: D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass\build npm ERR! gyp verb build dir “build” dir needed to be created? D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass\build npm ERR! gyp verb find vs2017 Found installation at: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools npm ERR! gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.VC.Tools.x86.x64 npm ERR! gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.Windows10SDK.19041 npm ERR! gyp verb find vs2017 - Found Microsoft.VisualStudio.VC.MSBuild.Base npm ERR! gyp verb find vs2017 - Using this installation with Windows 10 SDK npm ERR! gyp verb find vs2017 using installation: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools npm ERR! gyp verb build/config.gypi creating config file npm ERR! gyp verb build/config.gypi writing out config file: D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass\build\config.gypi npm ERR! (node:10764) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
npm ERR! (Use node --trace-deprecation ... to show where the warning was created) npm ERR! gyp verb config.gypi checking for gypi file: D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass\config.gypi npm ERR! gyp verb common.gypi checking for gypi file: D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass\common.gypi npm ERR! gyp verb gyp gyp format was not specified; forcing “msvs” npm ERR! gyp info spawn C:\Users\ASUS.windows-build-tools\python27\python.exe npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args ‘D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-gyp\gyp\gyp_main.py’, npm ERR! gyp info spawn args ‘binding.gyp’, npm ERR! gyp info spawn args ‘-f’, npm ERR! gyp info spawn args ‘msvs’, npm ERR! gyp info spawn args ‘-G’, npm ERR! gyp info spawn args ‘msvs_version=2015’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass\build\config.gypi’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-gyp\addon.gypi’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘C:\Users\ASUS\.node-gyp\16.8.0\include\node\common.gypi’, npm ERR! gyp info spawn args ‘-Dlibrary=shared_library’, npm ERR! gyp info spawn args ‘-Dvisibility=default’, npm ERR! gyp info spawn args ‘-Dnode_root_dir=C:\Users\ASUS\.node-gyp\16.8.0’, npm ERR! gyp info spawn args ‘-Dnode_gyp_dir=D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-gyp’, npm ERR! gyp info spawn args ‘-Dnode_lib_file=C:\Users\ASUS\.node-gyp\16.8.0\<(target_arch)\node.lib’, npm ERR! gyp info spawn args ‘-Dmodule_root_dir=D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass’, npm ERR! gyp info spawn args ‘-Dnode_engine=v8’, npm ERR! gyp info spawn args ‘–depth=.’, npm ERR! gyp info spawn args ‘–no-parallel’, npm ERR! gyp info spawn args ‘–generator-output’, npm ERR! gyp info spawn args ‘D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass\build’, npm ERR! gyp info spawn args ‘-Goutput_dir=.’ npm ERR! gyp info spawn args ] npm ERR! gyp verb command build [] npm ERR! gyp verb build type Release npm ERR! gyp verb architecture x64 npm ERR! gyp verb node dev dir C:\Users\ASUS.node-gyp\16.8.0 npm ERR! gyp verb found first Solution file build/binding.sln npm ERR! gyp verb using MSBuild: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\15.0\Bin\MSBuild.exe npm ERR! gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\15.0\Bin\MSBuild.exe npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args ‘build/binding.sln’, npm ERR! gyp info spawn args ‘/nologo’, npm ERR! gyp info spawn args ‘/p:Configuration=Release;Platform=x64’ npm ERR! gyp info spawn args ] npm ERR! gyp ERR! UNCAUGHT EXCEPTION npm ERR! gyp ERR! stack Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\15.0\Bin\MSBuild.exe ENOENT
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19) npm ERR! gyp ERR! stack at onErrorNT (node:internal/child_process:477:16) npm ERR! gyp ERR! stack at processTicksAndRejections (node:internal/process/task_queues:83:21) npm ERR! gyp ERR! System Windows_NT 10.0.19043 npm ERR! gyp ERR! command “C:\Program Files\nodejs\node.exe” “D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-gyp\bin\node-gyp.js” “rebuild” “–verbose” “–libsass_ext=” “–libsass_cflags=” “–libsass_ldflags=” “–libsass_library=” npm ERR! gyp ERR! cwd D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass npm ERR! gyp ERR! node -v v16.8.0 npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! gyp ERR! This is a bug in node-gyp. npm ERR! gyp ERR! Try to update node-gyp and file an Issue if it does not help: npm ERR! gyp ERR! https://github.com/nodejs/node-gyp/issues npm ERR! Build failed with error code: 7

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\ASUS\AppData\Local\npm-cache_logs\2021-08-28T11_49_37_792Z-debug.log

Expected behavior To be able to complete npm i and move on to the next step from README.md
Additional context (optional) I tried to run the following commands and these are their output:

npm install node-sass@latest

npm WARN deprecated set-value@2.0.0: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm WARN deprecated mixin-deep@1.3.1: Critical bug fixed in v2.0.1, please upgrade to the latest version. npm WARN deprecated ini@1.3.5: Please update to ini >=1.3.6 to avoid a prototype pollution issue npm WARN deprecated set-value@0.4.3: Critical bug fixed in v3.0.1, please upgrade to the latest version. npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated har-validator@5.0.3: this library is no longer supported npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated debug@4.0.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.0.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.0.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.0.1: Debug versions >=3.2.0 ❤️.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated travis-deploy-once@5.0.11: We recommend to use Travis Build Stages instead npm WARN deprecated @babel/polyfill @7.0.0: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information. npm WARN deprecated request@2.87.0: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated uuid@3.3.2: 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 mkdirp@0.5.1: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm WARN deprecated tar@2.2.1: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.
npm WARN deprecated core-js@2.5.7: core-js@❤️.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js. npm ERR! code 1 npm ERR! path D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\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:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\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:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\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@3.8.0 npm ERR! gyp info using node@16.8.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 check python checking for Python executable “C:\Users\ASUS.windows-build-tools\python27\python.exe” in the PATH npm ERR! gyp verb which succeeded C:\Users\ASUS.windows-build-tools\python27\python.exe C:\Users\ASUS.windows-build-tools\python27\python.exe npm ERR! gyp verb check python version C:\Users\ASUS\.windows-build-tools\python27\python.exe -c "import sys; print "2.7.15 npm ERR! gyp verb check python version .%s.%s" % sys.version_info[:3];" returned: %j npm ERR! gyp verb get node dir no --target version specified, falling back to host node version: 16.8.0 npm ERR! gyp verb command install [ ‘16.8.0’ ] npm ERR! gyp verb install input version string “16.8.0” npm ERR! gyp verb install installing version: 16.8.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: 16.8.0 npm ERR! gyp verb build dir attempting to create “build” dir: D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass\build npm ERR! gyp verb build dir “build” dir needed to be created? D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass\build npm ERR! gyp verb find vs2017 Found installation at: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools npm ERR! gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.VC.Tools.x86.x64 npm ERR! gyp verb find vs2017 - Found Microsoft.VisualStudio.Component.Windows10SDK.19041 npm ERR! gyp verb find vs2017 - Found Microsoft.VisualStudio.VC.MSBuild.Base npm ERR! gyp verb find vs2017 - Using this installation with Windows 10 SDK npm ERR! gyp verb find vs2017 using installation: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools npm ERR! gyp verb build/config.gypi creating config file npm ERR! gyp verb build/config.gypi writing out config file: D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass\build\config.gypi npm ERR! (node:6676) [DEP0150] DeprecationWarning: Setting process.config is deprecated. In the future the property will be read-only.
npm ERR! (Use node --trace-deprecation ... to show where the warning was created) npm ERR! gyp verb config.gypi checking for gypi file: D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass\config.gypi npm ERR! gyp verb common.gypi checking for gypi file: D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass\common.gypi npm ERR! gyp verb gyp gyp format was not specified; forcing “msvs” npm ERR! gyp info spawn C:\Users\ASUS.windows-build-tools\python27\python.exe npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args ‘D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-gyp\gyp\gyp_main.py’, npm ERR! gyp info spawn args ‘binding.gyp’, npm ERR! gyp info spawn args ‘-f’, npm ERR! gyp info spawn args ‘msvs’, npm ERR! gyp info spawn args ‘-G’, npm ERR! gyp info spawn args ‘msvs_version=2015’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass\build\config.gypi’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-gyp\addon.gypi’, npm ERR! gyp info spawn args ‘-I’, npm ERR! gyp info spawn args ‘C:\Users\ASUS\.node-gyp\16.8.0\include\node\common.gypi’, npm ERR! gyp info spawn args ‘-Dlibrary=shared_library’, npm ERR! gyp info spawn args ‘-Dvisibility=default’, npm ERR! gyp info spawn args ‘-Dnode_root_dir=C:\Users\ASUS\.node-gyp\16.8.0’, npm ERR! gyp info spawn args ‘-Dnode_gyp_dir=D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-gyp’, npm ERR! gyp info spawn args ‘-Dnode_lib_file=C:\Users\ASUS\.node-gyp\16.8.0\<(target_arch)\node.lib’, npm ERR! gyp info spawn args ‘-Dmodule_root_dir=D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass’, npm ERR! gyp info spawn args ‘-Dnode_engine=v8’, npm ERR! gyp info spawn args ‘–depth=.’, npm ERR! gyp info spawn args ‘–no-parallel’, npm ERR! gyp info spawn args ‘–generator-output’, npm ERR! gyp info spawn args ‘D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass\build’, npm ERR! gyp info spawn args ‘-Goutput_dir=.’ npm ERR! gyp info spawn args ] npm ERR! gyp verb command build [] npm ERR! gyp verb build type Release npm ERR! gyp verb architecture x64 npm ERR! gyp verb node dev dir C:\Users\ASUS.node-gyp\16.8.0 npm ERR! gyp verb found first Solution file build/binding.sln npm ERR! gyp verb using MSBuild: C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\15.0\Bin\MSBuild.exe npm ERR! gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\15.0\Bin\MSBuild.exe npm ERR! gyp info spawn args [ npm ERR! gyp info spawn args ‘build/binding.sln’, npm ERR! gyp info spawn args ‘/nologo’, npm ERR! gyp info spawn args ‘/p:Configuration=Release;Platform=x64’ npm ERR! gyp info spawn args ] npm ERR! gyp ERR! UNCAUGHT EXCEPTION npm ERR! gyp ERR! stack Error: spawn C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\15.0\Bin\MSBuild.exe ENOENT
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19) npm ERR! gyp ERR! stack at onErrorNT (node:internal/child_process:477:16) npm ERR! gyp ERR! stack at processTicksAndRejections (node:internal/process/task_queues:83:21) npm ERR! gyp ERR! System Windows_NT 10.0.19043 npm ERR! gyp ERR! command “C:\Program Files\nodejs\node.exe” “D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-gyp\bin\node-gyp.js” “rebuild” “–verbose” “–libsass_ext=” “–libsass_cflags=” “–libsass_ldflags=” “–libsass_library=” npm ERR! gyp ERR! cwd D:\Self-Guided\HTML-CSS\sass-fundamentals\node_modules\node-sass-middleware\node_modules\node-sass npm ERR! gyp ERR! node -v v16.8.0 npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! gyp ERR! This is a bug in node-gyp. npm ERR! gyp ERR! Try to update node-gyp and file an Issue if it does not help: npm ERR! gyp ERR! https://github.com/nodejs/node-gyp/issues npm ERR! Build failed with error code: 7

npm ERR! A complete log of this run can be found in: npm ERR! C:\Users\ASUS\AppData\Local\npm-cache_logs\2021-08-28T12_05_00_436Z-debug.log

node-sass seems to be available in global scope as i check its info with PowerShell Admin privilege:

Issue Analytics

State:
Created 2 years ago
Comments:5

Top GitHub Comments

2reactions

HelpMe-Plscommented, Dec 7, 2021

@Paritosh7 as expected, the issue seems to be the incompatible version of node-sass with nodeJS, so my solution is to downgrade nodeJS to the 14.17.6 version using nvm with these commands (if you don’t have it, download here: https://github.com/coreybutler/nvm-windows/releases): nvm install 14.17.6 then nvm use 14.17.6 then check node -v if it returns v14.17.6. If it does, proceed to npm i and start the exercises.

1reaction

Ren33000commented, Dec 1, 2021

I had a similar issue that couldn’t resolve until I saw this solution thank you so much!

My error was with commander and with the LTS version (14.17.6) it’s now working.

`sass-fundamentals git:(master) ./run -e nesting internal/modules/cjs/loader.js:883 throw err; ^

Error: Cannot find module ‘commander’ `

Top Results From Across the Web

error /node_modules/node-sass: Command failed

I then re-ran yarn install . Then I ran yarn add node-sass. That worked like a charm, after trying everything else above.

I can't install node-sass · Issue #3928 · nodejs/help - GitHub

When I run npm install node-sass --save ... npm ERR! command failed npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c ...

node-sass: Command failed when running npm install [Solved]

To solve the error node-sass: Command failed error, use the `sass` package instead of the deprecated `node-sass` module. Alternatively, install a version of ......

Why are my builds failing with a node-sass error? - Heroku Help

This can occur when you have compiled modules locally and checked the resulting node_modules folder into git before deploying. To fix this, we...

node-sass error node 16 | The AI Search Engine You Control

I fix it by following the following steps using a PowerShell with admin privileges: delete node_modules folder; running npm install --global windows-build-tools ...