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

cannot install this package? #1

Closed
mo opened this Issue Jun 18, 2017 · 6 comments

Comments

Projects
None yet
5 participants
@mo
Copy link

mo commented Jun 18, 2017

$ mkdir abc
$ cd abc
$ npm init -f
$ npm install --save-dev codeceptjs-webdriverio
npm WARN abc@1.0.0 No description
npm WARN abc@1.0.0 No repository field.

npm ERR! path /home/molsson/abc/node_modules/codeceptjs-webdriverio/node_modules/.bin/codeceptjs
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall chmod
npm ERR! enoent ENOENT: no such file or directory, chmod '/home/molsson/abc/node_modules/codeceptjs-webdriverio/node_modules/.bin/codeceptjs'
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! /home/molsson/.npm/_logs/2017-06-18T13_33_03_454Z-debug.log

If I install first "codeceptjs" and then "webdriverio" separately, it works just fine though.

$ node --version
v7.7.2
$ npm --version
5.0.3

@fatso83

This comment has been minimized.

Copy link

fatso83 commented Jun 19, 2017

Yeah, getting the same error. There seems to be a bug in how the right node_modules package is located. The layout would only be correct with version 2 of NPM, that had a hierarchical package layout structure. Nowadays you cannot assume that.

@Amdingo

This comment has been minimized.

Copy link

Amdingo commented Jul 11, 2017

+1 on this hopefully @DavertMik can provide some insight or update the lookup for .bin/

@DavertMik

This comment has been minimized.

Copy link
Owner

DavertMik commented Jul 11, 2017

Sorry, for the delay. I will take a look.

@sivnz

This comment has been minimized.

Copy link

sivnz commented Jul 12, 2017

+1 - Same error here.

@DavertMik

This comment has been minimized.

Copy link
Owner

DavertMik commented Jul 13, 2017

Thanks, this was fixed in 1.1.0 release. Please update
Yes, I was using old npm 3 and didn't get notice

@DavertMik DavertMik closed this Jul 13, 2017

@mo

This comment has been minimized.

Copy link

mo commented Jul 14, 2017

thanks for the fix @DavertMik

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment