npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'server' ]
2 info using npm@3.10.10
3 info using node@v6.12.0
4 verbose run-script [ 'preserver', 'server', 'postserver' ]
5 info lifecycle rin@0.0.0~preserver: rin@0.0.0
6 silly lifecycle rin@0.0.0~preserver: no script for preserver, continuing
7 info lifecycle rin@0.0.0~server: rin@0.0.0
8 verbose lifecycle rin@0.0.0~server: unsafe-perm in lifecycle true
9 verbose lifecycle rin@0.0.0~server: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/mnt/c/Users/Shatha/Documents/rin/node_modules/.bin:/home/Shatha/bin:/home/Shatha/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program Files (x86)/Intel/iCLS Client:/mnt/c/Program Files/Intel/iCLS Client:/mnt/c/Windows/System32/Npcap:/mnt/c/Windows/System32:/mnt/c/Windows:/mnt/c/Windows/System32/wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0:/mnt/c/Program Files (x86)/Microsoft SQL Server/90/Tools/Binn:/mnt/c/ProgramData/ComposerSetup/bin:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files/nodejs:/mnt/c/xampp/php:/mnt/c/Windows/System32/OpenSSH:/mnt/c/Program Files/Microsoft VS Code/bin:/mnt/c/Program Files/Intel/WiFi/bin:/mnt/c/Program Files/Common Files/Intel/WirelessCommon:/mnt/c/Python36/Scripts:/mnt/c/Python36:/mnt/c/Users/Shatha/AppData/Local/Microsoft/WindowsApps:/mnt/c/Program Files/Microsoft VS Code/bin:/mnt/c/Users/Shatha/AppData/Roaming/nvm:/mnt/c/Program Files/nodejs:/mnt/c/Users/Shatha/AppData/Local/atom/bin:/mnt/c/Users/Shatha/AppData/Roaming/npm:/snap/bin
10 verbose lifecycle rin@0.0.0~server: CWD: /mnt/c/Users/Shatha/Documents/rin
11 silly lifecycle rin@0.0.0~server: Args: [ '-c', 'cd client && npm run build && cd .. && npm start' ]
12 silly lifecycle rin@0.0.0~server: Returned: code: 1  signal: null
13 info lifecycle rin@0.0.0~server: Failed to exec server script
14 verbose stack Error: rin@0.0.0 server: `cd client && npm run build && cd .. && npm start`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:920:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid rin@0.0.0
16 verbose cwd /mnt/c/Users/Shatha/Documents/rin
17 error Linux 4.4.0-17134-Microsoft
18 error argv "/usr/bin/node" "/usr/bin/npm" "run" "server"
19 error node v6.12.0
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error rin@0.0.0 server: `cd client && npm run build && cd .. && npm start`
22 error Exit status 1
23 error Failed at the rin@0.0.0 server script 'cd client && npm run build && cd .. && npm start'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the rin package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     cd client && npm run build && cd .. && npm start
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs rin
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls rin
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]