/
npm-debug.log
19 lines (19 loc) · 1.15 KB
/
npm-debug.log
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@3.5.2
3 info using node@v8.10.0
4 verbose stack Error: ENOENT: no such file or directory, open '/home/blueplanet/Documents/workspace-spring-tool-suite-4-4.4.0.RELEASE/sicknesstorm/package.json'
5 verbose cwd /home/blueplanet/Documents/workspace-spring-tool-suite-4-4.4.0.RELEASE/sicknesstorm
6 error Linux 5.0.0-23-generic
7 error argv "/usr/bin/node" "/usr/bin/npm" "start"
8 error node v8.10.0
9 error npm v3.5.2
10 error path /home/blueplanet/Documents/workspace-spring-tool-suite-4-4.4.0.RELEASE/sicknesstorm/package.json
11 error code ENOENT
12 error errno -2
13 error syscall open
14 error enoent ENOENT: no such file or directory, open '/home/blueplanet/Documents/workspace-spring-tool-suite-4-4.4.0.RELEASE/sicknesstorm/package.json'
15 error enoent ENOENT: no such file or directory, open '/home/blueplanet/Documents/workspace-spring-tool-suite-4-4.4.0.RELEASE/sicknesstorm/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 [ -2, true ]