npm-debug.log

0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli   'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli   'start' ]
2 info using npm@3.10.8
3 info using node@v6.9.1
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle node@1.0.0~prestart: node@1.0.0
6 silly lifecycle node@1.0.0~prestart: no script for prestart, continuing
7 info lifecycle node@1.0.0~start: node@1.0.0
8 verbose lifecycle node@1.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle node@1.0.0~start: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\Prashant K Prajapati\Documents\GitHub\Attendence-System\node_modules\.bin;C:\Program Files (x86)\Intel\iCLS Client\;C:\Program Files\Intel\iCLS Client\;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files\Intel\Intel(R) Management Engine Components\IPT;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\HashiCorp\Vagrant\bin;C:\Program Files\nodejs\;c:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\;c:\Program Files\Microsoft SQL Server\110\Tools\Binn\;c:\Program Files\Microsoft SQL Server\110\DTS\Binn\;C:\Program Files\Cloud Foundry;C:\WINDOWS\system32\config\systemprofile\.dnx\bin;C:\Program Files\Microsoft DNX\Dnvm\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;;C:\Program Files (x86)\Microsoft VS Code\bin;C:\Users\Prashant K Prajapati\AppData\Local\Microsoft\WindowsApps;C:\Users\Prashant K Prajapati\AppData\Roaming\npm
10 verbose lifecycle node@1.0.0~start: CWD: C:\Users\Prashant K Prajapati\Documents\GitHub\Attendence-System
11 silly lifecycle node@1.0.0~start: Args: [ '/d /s /c', 'DEBUG=* node ./index ' ]
12 silly lifecycle node@1.0.0~start: Returned: code: 1  signal: null
13 info lifecycle node@1.0.0~start: Failed to exec start script
14 verbose stack Error: node@1.0.0 start: `DEBUG=* node ./index `
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (C:\Program Files\nodejs\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> (C:\Program Files\nodejs\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:877:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid node@1.0.0
16 verbose cwd C:\Users\Prashant K Prajapati\Documents\GitHub\Attendence-System
17 error Windows_NT 10.0.14393
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "start"
19 error node v6.9.1
20 error npm  v3.10.8
21 error code ELIFECYCLE
22 error node@1.0.0 start: `DEBUG=* node ./index `
22 error Exit status 1
23 error Failed at the node@1.0.0 start script 'DEBUG=* node ./index '.
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 node package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     DEBUG=* node ./index
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs node
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls node
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]