question-mark
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 install error

See original GitHub issue

When I try to install the packages I get this issue:

$ npm install

node-sass@3.13.1 install C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass node scripts/install.js

Downloading binary from https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-57_binding.node Cannot download “https://github.com/sass/node-sass/releases/download/v3.13.1/win32-x64-57_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@3.13.1 postinstall C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass node scripts/build.js

Building: C:\Program Files\nodejs\node.exe C:\github\ng2-admin\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 [ ‘C:\Program Files\nodejs\node.exe’, gyp verb cli ‘C:\github\ng2-admin\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 info using node-gyp@3.6.2 gyp info using node@8.11.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:\github\ng2-admin\node_modules\which\which.js:13:12) gyp verb which failed at F (C:\github\ng2-admin\node_modules\which\which.js:68:19) gyp verb which failed at E (C:\github\ng2-admin\node_modules\which\which.js:80:29) gyp verb which failed at C:\github\ng2-admin\node_modules\which\which.js:89:16 gyp verb which failed at C:\github\ng2-admin\node_modules\isexe\index.js:42:5 gyp verb which failed at C:\github\ng2-admin\node_modules\isexe\windows.js:36:5 gyp verb which failed at FSReqWrap.oncomplete (fs.js:152:21) gyp verb which failed python2 { Error: not found: python2 gyp verb which failed at getNotFoundError (C:\github\ng2-admin\node_modules\which\which.js:13:12) gyp verb which failed at F (C:\github\ng2-admin\node_modules\which\which.js:68:19) gyp verb which failed at E (C:\github\ng2-admin\node_modules\which\which.js:80:29) gyp verb which failed at C:\github\ng2-admin\node_modules\which\which.js:89:16 gyp verb which failed at C:\github\ng2-admin\node_modules\isexe\index.js:42:5 gyp verb which failed at C:\github\ng2-admin\node_modules\isexe\windows.js:36:5 gyp verb which failed at FSReqWrap.oncomplete (fs.js:152:21) gyp verb which failed stack: ‘Error: not found: python2\n at getNotFoundError (C:\github\ng2-admin\node_modules\which\which.js:13:12)\n at F (C:\github\ng2-admin\node_modules\which\which.js:68:19)\n at E (C:\github\ng2-admin\node_modules\which\which.js:80:29)\n at C:\github\ng2-admin\node_modules\which\which.js:89:16\n at C:\github\ng2-admin\node_modules\isexe\index.js:42:5\n at C:\github\ng2-admin\node_modules\isexe\windows.js:36:5\n at FSReqWrap.oncomplete (fs.js:152:21)’, gyp verb which failed code: ‘ENOENT’ } gyp verb check python checking for Python executable “python” in the PATH gyp verb which succeeded python C:\Program Files (x86)\Python27\python.EXE gyp verb check python version C:\Program Files (x86)\Python27\python.EXE -c "import platform; print(platform.python_version());" returned: “2.7.15\r\n” gyp verb get node dir no --target version specified, falling back to host node version: 8.11.1 gyp verb command install [ ‘8.11.1’ ] gyp verb install input version string “8.11.1” gyp verb install installing version: 8.11.1 gyp verb install --ensure was passed, so won’t reinstall if already installed gyp verb install version is already installed, need to check “installVersion” gyp verb got “installVersion” 9 gyp verb needs “installVersion” 9 gyp verb install version is good gyp verb get node dir target node version installed: 8.11.1 gyp verb build dir attempting to create “build” dir: C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build gyp verb build dir “build” dir needed to be created? C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build gyp verb find vs2017 Found installation at: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community gyp verb find vs2017 - Found Microsoft.VisualStudio.VC.MSBuild.Base gyp verb find vs2017 - Missing VC++ 2017 v141 toolset (x86,x64) (Microsoft.VisualStudio.Component.VC.Tools.x86.x64) gyp verb find vs2017 - Missing a Windows SDK (Microsoft.VisualStudio.Component.Windows10SDK.* or Microsoft.VisualStudio.Component.Windows81SDK) gyp verb find vs2017 - Some required components are missing, not using this installation gyp verb Not using VS2017: No usable installation of VS2017 found gyp verb build/config.gypi creating config file gyp verb build/config.gypi writing out config file: C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build\config.gypi gyp verb config.gypi checking for gypi file: C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\config.gypi gyp verb common.gypi checking for gypi file: C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\common.gypi gyp verb gyp gyp format was not specified; forcing “msvs” gyp info spawn C:\Program Files (x86)\Python27\python.EXE gyp info spawn args [ ‘C:\github\ng2-admin\node_modules\node-gyp\gyp\gyp_main.py’, gyp info spawn args ‘binding.gyp’, gyp info spawn args ‘-f’, gyp info spawn args ‘msvs’, gyp info spawn args ‘-G’, gyp info spawn args ‘msvs_version=auto’, gyp info spawn args ‘-I’, gyp info spawn args ‘C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build\config.gypi’, gyp info spawn args ‘-I’, gyp info spawn args ‘C:\github\ng2-admin\node_modules\node-gyp\addon.gypi’, gyp info spawn args ‘-I’, gyp info spawn args ‘C:\Users\danyb\.node-gyp\8.11.1\include\node\common.gypi’, gyp info spawn args ‘-Dlibrary=shared_library’, gyp info spawn args ‘-Dvisibility=default’, gyp info spawn args ‘-Dnode_root_dir=C:\Users\danyb\.node-gyp\8.11.1’, gyp info spawn args ‘-Dnode_gyp_dir=C:\github\ng2-admin\node_modules\node-gyp’, gyp info spawn args ‘-Dnode_lib_file=C:\Users\danyb\.node-gyp\8.11.1\<(target_arch)\node.lib’, gyp info spawn args ‘-Dmodule_root_dir=C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass’, gyp info spawn args ‘-Dnode_engine=v8’, gyp info spawn args ‘–depth=.’, gyp info spawn args ‘–no-parallel’, gyp info spawn args ‘–generator-output’, gyp info spawn args ‘C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build’, gyp info spawn args ‘-Goutput_dir=.’ ] gyp verb command build [] gyp verb build type Release gyp verb architecture x64 gyp verb node dev dir C:\Users\danyb.node-gyp\8.11.1 gyp verb found first Solution file build/binding.sln gyp verb could not find “msbuild.exe” in PATH - finding location in registry gyp info spawn C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe gyp info spawn args [ ‘build/binding.sln’, gyp info spawn args ‘/nologo’, gyp info spawn args ‘/p:Configuration=Release;Platform=x64’ ] Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu erm▒glichen, m▒ssen Sie den Schalter “/m” hinzuf▒gen. Der Buildvorgang wurde am 05.05.2018 20:00:46 gestartet. Projekt “C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build\binding.sln” auf Knoten “1” (Standardziele). ValidateSolutionConfiguration: Die Projektmappenkonfiguration “Release|x64” wird erstellt. MSBUILD : error MSB3428: Die Visual C+±Komponente “VCBuild.exe” konnte nicht geladen werden. Um dieses Problem zu beheben, installieren Sie entweder 1) .NET Framework 2.0 SDK oder 2) Microsoft Visual Studio 2005 oder 3) f▒gen Sie den Speicherort der Komponente zum Systempfad hinzu, falls er vom Standardspeicherort abweicht. [C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build\binding.sln] Die Erstellung des Projekts “C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build\binding.sln” ist abgeschlossen (Standardziele) – FEHLER.

Fehler beim Buildvorgang.

“C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build\binding.sln” (Standardziel) (1) -> (src\libsass Ziel) -> MSBUILD : error MSB3428: Die Visual C+±Komponente “VCBuild.exe” konnte nicht geladen werden. Um dieses Problem zu beheben, installieren Sie entweder 1) .NET Framework 2.0 SDK oder 2) Microsoft Visual Studio 2005 oder 3) f▒gen Sie den Speicherort der Komponente zum Systempfad hinzu, falls er vom Standardspeicherort abweicht. [C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass\build\binding.sln]

0 Warnung(en)
1 Fehler

Verstrichene Zeit 00:00:00.08 gyp ERR! build error gyp ERR! stack Error: C:\Windows\Microsoft.NET\Framework\v4.0.30319\msbuild.exe failed with exit code: 1 gyp ERR! stack at ChildProcess.onExit (C:\github\ng2-admin\node_modules\node-gyp\lib\build.js:258:23) gyp ERR! stack at emitTwo (events.js:126:13) gyp ERR! stack at ChildProcess.emit (events.js:214:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:198:12) gyp ERR! System Windows_NT 10.0.16299 gyp ERR! command “C:\Program Files\nodejs\node.exe” “C:\github\ng2-admin\node_modules\node-gyp\bin\node-gyp.js” “rebuild” “–verbose” “–libsass_ext=” “–libsass_cflags=” “–libsass_ldflags=” “–libsass_library=” gyp ERR! cwd C:\github\ng2-admin\node_modules\wintersmith-sassy\node_modules\node-sass gyp ERR! node -v v8.11.1 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok Build failed with error code: 1 npm WARN angular2-datatable@0.6.0 requires a peer of @angular/core@^2.0.0 but none is installed. You must install peer dependencies yourself. npm WARN angular2-datatable@0.6.0 requires a peer of @angular/common@^2.0.0 but none is installed. You must install peer dependencies yourself. npm WARN angular2-datatable@0.6.0 requires a peer of @angular/platform-browser@^2.0.0 but none is installed. You must install peer dependencies yourself. npm WARN ng2-ckeditor@1.1.6 requires a peer of @angular/core@^2.1.0 but none is installed. You must install peer dependencies yourself. npm WARN ng2-ckeditor@1.1.6 requires a peer of @angular/forms@^2.1.0 but none is installed. You must install peer dependencies yourself. npm WARN ng2-ckeditor@1.1.6 requires a peer of @angular/common@^2.1.0 but none is installed. You must install peer dependencies yourself. npm WARN ng2-handsontable@0.48.0 requires a peer of @angular/common@^2.3.1 but none is installed. You must install peer dependencies yourself. npm WARN ng2-handsontable@0.48.0 requires a peer of @angular/compiler@^2.3.1 but none is installed. You must install peer dependencies yourself. npm WARN ng2-handsontable@0.48.0 requires a peer of @angular/core@^2.3.1 but none is installed. You must install peer dependencies yourself. npm WARN ng2-handsontable@0.48.0 requires a peer of @angular/forms@^2.3.1 but none is installed. You must install peer dependencies yourself. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.2 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.2: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! node-sass@3.13.1 postinstall: node scripts/build.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the node-sass@3.13.1 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\danyb\AppData\Roaming\npm-cache_logs\2018-05-05T18_00_47_778Z-debug.log

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:11

github_iconTop GitHub Comments

1reaction
jovelromeocommented, Jun 12, 2019

Thank, i already solve this. I was missing node-gyp. Solved this with

npm install --global --production windows-build-tools
npm install -g node-gyp
0reactions
fsmaili77commented, Apr 21, 2022

Under Ubuntu 20.04, I have solved the problem by modifying the file package.json (the dependency: “node-sass”: “xx.xx.x” by “sass”: “^1.49.0”. As explained by @fabiocanon After this I have executed the following commands:

sudo apt-get update sudo apt-get install build-essential

And finally with npm start I have succeded to launch the project.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Common errors | npm Docs
Possible temporary npm registry glitch, or corrupted local server cache. Run npm cache clean and/or try again later. · This can be caused...
Read more >
npm install error from the terminal - Stack Overflow
Running just "npm install" will look for dependencies listed in your package.json. The error you're getting says that you don't have a ...
Read more >
How to solve npm ERR! code 1 when running npm install
Fix npm error code 1 by updating your dependencies · Update one package version in package.json file · Then run npm install ·...
Read more >
NPM install error - Material Design for Bootstrap
Trying to install MDB pro 4.19.2 just downloaded and ran npm install but getting this error of sha512 not matching. Can someone tell...
Read more >
Step by step solution for npm install error - M220JS - MongoDB
Delete the package-lock. · If you see a lot of warning & error messages related to npm-gyp, run npm rebuild & this should...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found