knowledge/npm-debug.log at master · crasite/knowledge · GitHub

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
47
48
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   'run',
1 verbose cli   'test' ]
2 info using npm@3.10.10
3 info using node@v6.11.3
4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle knowledge@1.0.0~pretest: knowledge@1.0.0
6 silly lifecycle knowledge@1.0.0~pretest: no script for pretest, continuing
7 info lifecycle knowledge@1.0.0~test: knowledge@1.0.0
8 verbose lifecycle knowledge@1.0.0~test: unsafe-perm in lifecycle true
9 verbose lifecycle knowledge@1.0.0~test: PATH: C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin;C:\Develop\knowledge\node_modules\.bin;C:\Program Files\Microsoft MPI\Bin\;C:\ProgramData\Oracle\Java\javapath;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:\Program Files (x86)\GtkSharp\2.12\bin;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;C:\Program Files\dotnet\;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Users\tpcra\AppData\Local\Microsoft\WindowsApps;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;C:\Users\tpcra\AppData\Roaming\npm;C:\Users\tpcra\AppData\Local\atom\bin;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\Heroku\bin;C:\Users\tpcra\AppData\Local\Microsoft\WindowsApps;
10 verbose lifecycle knowledge@1.0.0~test: CWD: C:\Develop\knowledge
11 silly lifecycle knowledge@1.0.0~test: Args: [ '/d /s /c', 'ava-ts --watch' ]
12 silly lifecycle knowledge@1.0.0~test: Returned: code: 3  signal: null
13 info lifecycle knowledge@1.0.0~test: Failed to exec test script
14 verbose stack Error: knowledge@1.0.0 test: `ava-ts --watch`
14 verbose stack Exit status 3
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:920:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid knowledge@1.0.0
16 verbose cwd C:\Develop\knowledge
17 error Windows_NT 10.0.16299
18 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "test"
19 error node v6.11.3
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error knowledge@1.0.0 test: `ava-ts --watch`
22 error Exit status 3
23 error Failed at the knowledge@1.0.0 test script 'ava-ts --watch'.
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 knowledge package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     ava-ts --watch
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs knowledge
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls knowledge
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]