NPM Install Failing for v1.15.0
Closed this issue · 10 comments
Trying to install latest version throws an error:
$ npm install geckodriver
npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm ERR! path /Users/efrain/Documents/automation/kp/js-automation/ylva/node_modules/geckodriver/bin/geckodriver
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/Users/efrain/Documents/automation/kp/js-automation/ylva/node_modules/geckodriver/bin/geckodriver'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/efrain/.npm/_logs/2019-02-15T23_27_38_892Z-debug.log
Installing the previous version works fine.
$ npm install geckodriver@1.14.1
> geckodriver@1.14.1 postinstall /Users/efrain/Documents/automation/kp/js-automation/ylva/node_modules/geckodriver
> node index.js
Downloading geckodriver... Extracting... Complete.
npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.
+ geckodriver@1.14.1
added 2 packages from 9 contributors in 14.268s
$ npm ls geckodriver
kp-webdriverjs-utils@5.1.0-next.14 /Users/efrain/Documents/automation/kp/js-automation/ylva
└── geckodriver@1.14.1
EDIT: Adding OS
Attempting to install on both Linux (Redhat) with Node v8.11.3 and npm v3.10.10
Mac OS 10.14.3 - Node v8.14.0, npm 6.4.1
this happened to me too
same here, node 10
Same issue for me as well
me too
Same for me on Windows 10, node 10.14.2
some for me
I will investigate what went wrong with this version tomorrow morning, sorry about that!
Please try with 1.15.1. It seems like lates version of npm started ignoring published files differently, so a file went missing in the earlier release.
Please try with 1.15.1. It seems like lates version of npm started ignoring published files differently, so a file went missing in the earlier release.
Thank you @vladikoff , issue is now resolved.