-
Notifications
You must be signed in to change notification settings - Fork 29.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Install npm packages in windows gives node-gyp error #29310
Comments
8 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents@0.3.8 (node_modules\fsevents):
36159 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@0.3.8: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
36160 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: darwin
36160 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any
36160 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: win32
36160 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
36161 verbose stack Error: oniguruma@6.1.1 install: `node-gyp rebuild`
36161 verbose stack Exit status 1
36161 verbose stack at EventEmitter.<anonymous> (C:\Users\stefan.schneider\AppData\Local\nvs\node\7.4.0\x64\node_modules\npm\lib\utils\lifecycle.js:279:16)
36161 verbose stack at emitTwo (events.js:106:13)
36161 verbose stack at EventEmitter.emit (events.js:191:7)
36161 verbose stack at ChildProcess.<anonymous> (C:\Users\stefan.schneider\AppData\Local\nvs\node\7.4.0\x64\node_modules\npm\lib\utils\spawn.js:40:14)
36161 verbose stack at emitTwo (events.js:106:13)
36161 verbose stack at ChildProcess.emit (events.js:191:7)
36161 verbose stack at maybeClose (internal/child_process.js:885:16)
36161 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
36162 verbose pkgid oniguruma@6.1.1
36163 verbose cwd D:\repositories\git\vscode
36164 error Windows_NT 10.0.14393
|
same for npm ERR! node v6.11.0
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE |
Can confirm when attempting to setup local environment for working on a pull request. |
I was able to solve this doing the following:
|
For me it was necessary to also set the |
I had the same issue (I had VS Express 2008, Build Tools 2015, and Build Tools 2017 installed). Thanks to con-ssc's post above, I resolved it using
alone. I didn't have to perform the To add some background information, here's what I think happened (at least in my case): according to this issue node-gyp doesn't currently support VS 2017 and falls back to VS 2015. However as the Readme for v3.6.2 says
so one would either have to do either one of these
|
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: