-
Notifications
You must be signed in to change notification settings - Fork 0
/
npm-debug.log
23 lines (23 loc) · 1.11 KB
/
npm-debug.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
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 'start' ]
2 info using npm@3.10.10
3 info using node@v6.10.2
4 verbose stack Error: ENOENT: no such file or directory, open 'C:\Sites\twitter_scheduler\package.json'
4 verbose stack at Error (native)
5 verbose cwd C:\Sites\twitter_scheduler
6 error Windows_NT 10.0.16299
7 error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "start"
8 error node v6.10.2
9 error npm v3.10.10
10 error path C:\Sites\twitter_scheduler\package.json
11 error code ENOENT
12 error errno -4058
13 error syscall open
14 error enoent ENOENT: no such file or directory, open 'C:\Sites\twitter_scheduler\package.json'
15 error enoent ENOENT: no such file or directory, open 'C:\Sites\twitter_scheduler\package.json'
15 error enoent This is most likely not a problem with npm itself
15 error enoent and is related to npm not being able to find a file.
16 verbose exit [ -4058, true ]