forked from jrainlau/draw-something
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathnpm-debug.log
More file actions
46 lines (46 loc) · 3.2 KB
/
npm-debug.log
File metadata and controls
46 lines (46 loc) · 3.2 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
0 info it worked if it ends with ok
1 verbose cli [ 'D:\\nodejs\\node.exe',
1 verbose cli 'D:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'dev' ]
2 info using npm@3.3.12
3 info using node@v5.4.1
4 verbose run-script [ 'predev', 'dev', 'postdev' ]
5 info lifecycle draw-something@1.0.0~predev: draw-something@1.0.0
6 silly lifecycle draw-something@1.0.0~predev: no script for predev, continuing
7 info lifecycle draw-something@1.0.0~dev: draw-something@1.0.0
8 verbose lifecycle draw-something@1.0.0~dev: unsafe-perm in lifecycle true
9 verbose lifecycle draw-something@1.0.0~dev: PATH: D:\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Users\Administrator\Desktop\draw-something\node_modules\.bin;C:\Users\Administrator\bin;D:\Git\mingw64\bin;D:\Git\usr\local\bin;D:\Git\usr\bin;D:\Git\usr\bin;D:\Git\mingw64\bin;D:\Git\usr\bin;C:\Users\Administrator\bin;C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x86;C:\Program Files (x86)\Intel\OpenCL SDK\2.0\bin\x64;D:\Git\cmd;D:\nodejs;D:\AppServ\php5;D:\mongodb\bin;C:\Program Files\OpenVPN\bin;C:\Users\Administrator\AppData\Roaming\npm;D:\AppServ\Apache24\bin;D:\AppServ\MySQL\bin;D:\Git\usr\bin\vendor_perl;D:\Git\usr\bin\core_perl
10 verbose lifecycle draw-something@1.0.0~dev: CWD: C:\Users\Administrator\Desktop\draw-something
11 silly lifecycle draw-something@1.0.0~dev: Args: [ '/d /s /c', 'node server.js' ]
12 silly lifecycle draw-something@1.0.0~dev: Returned: code: 1 signal: null
13 info lifecycle draw-something@1.0.0~dev: Failed to exec dev script
14 verbose stack Error: draw-something@1.0.0 dev: `node server.js`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (D:\nodejs\node_modules\npm\lib\utils\lifecycle.js:232:16)
14 verbose stack at emitTwo (events.js:87:13)
14 verbose stack at EventEmitter.emit (events.js:172:7)
14 verbose stack at ChildProcess.<anonymous> (D:\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
14 verbose stack at emitTwo (events.js:87:13)
14 verbose stack at ChildProcess.emit (events.js:172:7)
14 verbose stack at maybeClose (internal/child_process.js:821:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
15 verbose pkgid draw-something@1.0.0
16 verbose cwd C:\Users\Administrator\Desktop\draw-something
17 error Windows_NT 6.1.7601
18 error argv "D:\\nodejs\\node.exe" "D:\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "dev"
19 error node v5.4.1
20 error npm v3.3.12
21 error code ELIFECYCLE
22 error draw-something@1.0.0 dev: `node server.js`
22 error Exit status 1
23 error Failed at the draw-something@1.0.0 dev script 'node server.js'.
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 draw-something package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error node server.js
23 error You can get their info via:
23 error npm owner ls draw-something
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]