-
Notifications
You must be signed in to change notification settings - Fork 27.4k
Repository can't npm install #14200
Comments
Regarding the first issue, our current setup is indeed not (yet) compatible with npm v3.x. FWIW, node-gyp error (even if pretty bold and scary) don't necessarily mean that the installation failed (they are common on Windows). Are you sure that |
I will go ahead and close this since our current incompatibility with npm v3.x is tracked in another issue, but feel free to continue the discussion below. You might also want to try your luck on one of the general support channels. Maybe someone has some experience with setting up Angular's development environment on npm v3.x. |
Thanks for your response, @gkalpak. I tried to move forward from the npm install, despite the issues, and run |
The fact that Now regarding the I've been running into this myself lately. It had something to do with our version of Protractor relying on an older version of ChromeDriver (that is somehow not compatible with certain combinations of Chrome and Windows versions and other unknown factors). So, while we're dealing with this issue, you can |
BTW, you can download the latest ChromeDriver here. |
I'm on the Microsoft Edge web platform team and we're trying to automate Angular's tests in our browser. We're encounter multiple issues blocking an npm install on Windows.
The first issue is that with npm 3+ the preinstall script is running after the install and purging the
node_modules
folder. This is covered in bug #13123.This can be mitigated by renaming the
preinstall
script and running it manually.However, then after running
npm i
again Windows users will see node-gyp build issues.I have tried the following among many other mitigations with no success.
GYP_MSVS_VERSION=2015
npm install -g --msvs_version=2015 node-gyp rebuild
npm config set msvs_version 2015
and with--global
Any help would be appreciated.
The text was updated successfully, but these errors were encountered: