Skip to content
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

cmd.js fails #51

Closed
konatachan opened this issue Apr 26, 2014 · 2 comments
Closed

cmd.js fails #51

konatachan opened this issue Apr 26, 2014 · 2 comments

Comments

@konatachan
Copy link

@konatachan konatachan commented Apr 26, 2014

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.js
10 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 ]

@konatachan konatachan changed the title cmd,js fails cmd.js fails Apr 26, 2014
@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Apr 26, 2014

Looking into it

@feross

This comment has been minimized.

Copy link
Member

@feross feross commented Apr 26, 2014

Okay, I just published a new version (0.2.6) that doesn't give this error. Run npm update -g webtorrent. However, I don't expect the actual torrent downloading to work. I'm in the middle of a refactor of bittorrent-client and things are a bit broke at the moment. I expect this to be fixed soon.

@feross feross closed this Apr 26, 2014
@lock lock bot locked as resolved and limited conversation to collaborators May 7, 2018
bricewge pushed a commit to bricewge/webtorrent that referenced this issue May 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.