Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign upcmd.js fails #51
Closed
cmd.js fails #51
Comments
This comment has been minimized.
This comment has been minimized.
|
Looking into it |
This comment has been minimized.
This comment has been minimized.
|
Okay, I just published a new version (0.2.6) that doesn't give this error. Run |
bricewge
pushed a commit
to bricewge/webtorrent
that referenced
this issue
May 11, 2018
Closes webtorrent#51
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
getting this
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@1.4.3
3 info using node@v0.10.26
4 verbose node symlink /usr/bin/node
5 verbose run-script [ 'prestart', 'start', 'poststart' ]
6 info prestart webtorrent@0.2.5
7 info start webtorrent@0.2.5
8 verbose unsafe-perm in lifecycle true
9 info webtorrent@0.2.5 Failed to exec start script
10 error webtorrent@0.2.5 start:
./bin/cmd.js10 error Exit status 8
11 error Failed at the webtorrent@0.2.5 start script.
11 error This is most likely a problem with the webtorrent package,
11 error not with npm itself.
11 error Tell the author that this fails on your system:
11 error ./bin/cmd.js
11 error You can get their info via:
11 error npm owner ls webtorrent
11 error There is likely additional logging output above.
12 error System Linux 3.11.0-12-generic
13 error command "/usr/bin/node" "/usr/bin/npm" "start"
14 error cwd /home/web/webtorrent
15 error node -v v0.10.26
16 error npm -v 1.4.3
17 error code ELIFECYCLE
18 verbose exit [ 1, true ]