0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose node symlink /usr/bin/node
5 verbose run-script [ 'prestart', 'start', 'poststart' ]
6 info prestart [email protected]
7 info start [email protected]
8 verbose unsafe-perm in lifecycle true
9 info [email protected] Failed to exec start script
10 verbose stack Error: [email protected] start: `node server.js`
10 verbose stack Exit status 1
10 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:213:16)
10 verbose stack     at EventEmitter.emit (events.js:110:17)
10 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
10 verbose stack     at ChildProcess.emit (events.js:110:17)
10 verbose stack     at maybeClose (child_process.js:1015:16)
10 verbose stack     at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
11 verbose pkgid [email protected]
12 verbose cwd /root/hack.chat
13 error Linux 3.19.0-22-generic
14 error argv "/usr/bin/node" "/usr/bin/npm" "start"
15 error node v0.12.7
16 error npm  v2.11.3
17 error code ELIFECYCLE
18 error [email protected] start: `node server.js`
18 error Exit status 1
19 error Failed at the [email protected] start script 'node server.js'.
19 error This is most likely a problem with the hack.chat package,
19 error not with npm itself.
19 error Tell the author that this fails on your system:
19 error     node server.js
19 error You can get their info via:
19 error     npm owner ls hack.chat
19 error There is likely additional logging output above.
20 verbose exit [ 1, true ]