0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm@6.9.0
3 info using node@v8.11.4
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle gcleht@0.0.0~prestart: gcleht@0.0.0
6 info lifecycle gcleht@0.0.0~start: gcleht@0.0.0
7 verbose lifecycle gcleht@0.0.0~start: unsafe-perm in lifecycle true
8 verbose lifecycle gcleht@0.0.0~start: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/toicc/Documents/gc leht/gcleht/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin
9 verbose lifecycle gcleht@0.0.0~start: CWD: /home/toicc/Documents/gc leht/gcleht
10 silly lifecycle gcleht@0.0.0~start: Args: [ '-c', 'node keystone.js' ]
11 silly lifecycle gcleht@0.0.0~start: Returned: code: 1  signal: null
12 info lifecycle gcleht@0.0.0~start: Failed to exec start script
13 verbose stack Error: gcleht@0.0.0 start: `node keystone.js`
13 verbose stack Exit status 1
13 verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at EventEmitter.emit (events.js:214:7)
13 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack     at emitTwo (events.js:126:13)
13 verbose stack     at ChildProcess.emit (events.js:214:7)
13 verbose stack     at maybeClose (internal/child_process.js:925:16)
13 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
14 verbose pkgid gcleht@0.0.0
15 verbose cwd /home/toicc/Documents/gc leht/gcleht
16 verbose Linux 4.18.0-17-lowlatency
17 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v8.11.4
19 verbose npm  v6.9.0
20 error code ELIFECYCLE
21 error errno 1
22 error gcleht@0.0.0 start: `node keystone.js`
22 error Exit status 1
23 error Failed at the gcleht@0.0.0 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]