-
Notifications
You must be signed in to change notification settings - Fork 0
/
npm-debug.log
40 lines (40 loc) · 1.93 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
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'watch' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prewatch', 'watch', 'postwatch' ]
5 info prewatch [email protected]
6 info watch [email protected]
7 verbose unsafe-perm in lifecycle true
8 info [email protected] Failed to exec watch script
9 verbose stack Error: [email protected] watch: `npx parcel watch ./src/cabothouse.js -d build --no-hmr`
9 verbose stack spawn ENOENT
9 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:17:16)
9 verbose stack at emitTwo (events.js:87:13)
9 verbose stack at ChildProcess.emit (events.js:172:7)
9 verbose stack at maybeClose (internal/child_process.js:862:16)
9 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:222:5)
10 verbose pkgid [email protected]
11 verbose cwd /home/cabothf/staging.cabothouse.com/wp-content/themes/cabothouse
12 error Linux 3.10.0-962.3.2.lve1.5.28.el7.x86_64
13 error argv "/usr/bin/node" "/usr/bin/npm" "run" "watch"
14 error node v4.9.1
15 error npm v2.15.11
16 error file sh
17 error code ELIFECYCLE
18 error errno ENOENT
19 error syscall spawn
20 error [email protected] watch: `npx parcel watch ./src/cabothouse.js -d build --no-hmr`
20 error spawn ENOENT
21 error Failed at the [email protected] watch script 'npx parcel watch ./src/cabothouse.js -d build --no-hmr'.
21 error This is most likely a problem with the cabothouse package,
21 error not with npm itself.
21 error Tell the author that this fails on your system:
21 error npx parcel watch ./src/cabothouse.js -d build --no-hmr
21 error You can get information on how to open an issue for this project with:
21 error npm bugs cabothouse
21 error Or if that isn't available, you can get their info via:
21 error
21 error npm owner ls cabothouse
21 error There is likely additional logging output above.
22 verbose exit [ 1, true ]