node-chromedriver: Failed at the chromedriver@2.21.2 install script 'node install.js'.
npm WARN deprecated npmconf@2.1.2: this package has been reintegrated into npm and is now out of date with respect to npm
chromedriver@2.21.2 install D:\Workspaces\VueProjects\testvue1\node_modules\chromedriver node install.js
Downloading http://chromedriver.storage.googleapis.com/2.21/chromedriver_win32.zip Saving to C:\Users\liyun\AppData\Local\Temp\chromedriver\chromedriver_win32.zip Receiving… ChromeDriver installation failed undefined npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.12 npm ERR! Windows_NT 10.0.14332 npm ERR! argv “D:\Dev\nodejs\node.exe” “D:\Dev\nodejs\node_modules\npm\bin\npm-cli.js” “i” “chromedriver@2.21.2” npm ERR! node v6.1.0 npm ERR! npm v3.8.6 npm ERR! code ELIFECYCLE
npm ERR! chromedriver@2.21.2 install: node install.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the chromedriver@2.21.2 install script ‘node install.js’.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the chromedriver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node install.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs chromedriver
npm ERR! Or if that isn’t available, you can get their info via:
npm ERR! npm owner ls chromedriver
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request: npm ERR! D:\Workspaces\VueProjects\testvue1\npm-debug.log
About this issue
- Original URL
- State: closed
- Created 8 years ago
- Comments: 18 (4 by maintainers)
Have a try: npm install chromedriver --chromedriver_cdnurl=http://cdn.npm.taobao.org/dist/chromedriver
@FrankStraif Thank you so much! Disabling proxy(and a
npm cache clear) solved the problem.I had the same issue, and for me it was a “behind proxy” issue. The install.js file is using a proxy from npms ‘proxy’ setting. Adding “proxy=http://…” to my .npmrc solved the issue for me. I found it by checking what was the content of the downloaded zip file: it wan an html error page and not the zip. A very common error if you do not check the http result of a http-get call.
@peter-mouland Yes, that is being fixed. They pulled the 32 bit version from the repo. We will be updating it today. The update is already in the
masterbranch.