Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unmet dependency color, npm start #15

Open
JustFly1984 opened this issue Jul 20, 2015 · 1 comment
Open

unmet dependency color, npm start #15

JustFly1984 opened this issue Jul 20, 2015 · 1 comment

Comments

@JustFly1984
Copy link

this is log file

0 info it worked if it ends with ok
1 verbose cli [ 'node', '/usr/local/bin/npm', 'start' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info prestart [email protected]
6 info start [email protected]
7 verbose unsafe-perm in lifecycle true
8 info [email protected] Failed to exec start script
9 verbose stack Error: [email protected] start: webpack-dev-server --progress --colors
9 verbose stack spawn ENOENT
9 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:17:16)
9 verbose stack at ChildProcess.emit (events.js:110:17)
9 verbose stack at maybeClose (child_process.js:1015:16)
9 verbose stack at Process.ChildProcess._handle.onexit (child_process.js:1087:5)
10 verbose pkgid [email protected]
11 verbose cwd /Users/justfly/sandbox/paths
12 error Darwin 14.3.0
13 error argv "node" "/usr/local/bin/npm" "start"
14 error node v0.12.6
15 error npm v2.11.2
16 error file sh
17 error code ELIFECYCLE
18 error errno ENOENT
19 error syscall spawn
20 error [email protected] start: webpack-dev-server --progress --colors
20 error spawn ENOENT
21 error Failed at the [email protected] start script 'webpack-dev-server --progress --colors'.
21 error This is most likely a problem with the paths package,
21 error not with npm itself.
21 error Tell the author that this fails on your system:
21 error webpack-dev-server --progress --colors
21 error You can get their info via:
21 error npm owner ls paths
21 error There is likely additional logging output above.
22 verbose exit [ 1, true ]

@jxnblk
Copy link
Owner

jxnblk commented Jul 21, 2015

I'm not really sure what's happening here. I am using npm 3, so I'll double check and make sure all the dependencies are in package.json.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants