-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Unhandled 'error' event #167
Comments
Node 6 has issues on Windows. I suggest installing 5.11.1 |
Thanks for immediate response. I was able to use the startup kit you had for Pluralsight course fine without any issues though. Thanks, Ganesh
|
Hrmm. Interesting. Perhaps this would help? http://stackoverflow.com/questions/27688804/how-do-i-debug-error-spawn-enoent-on-node-js |
Unhandled 'error' event #167 events.js:167 Error: EPERM: operation not permitted, lstat 'F:\tf\android\app\build\generated\source\r\debug\android\arch\core\R.java' npm ERR! A complete log of this run can be found in: F:\tf>npm -v F:\tf>node -v |
did you found the solution i am also facing the same issue |
Node version:6.2.1
npm version:3.9.3
Operating system:Windows
Command line used:npm start
Steps to reproduce:
[BS] Serving files from: src
npm-debug.txt
[BS] Watching files...
events.js:160
throw er; // Unhandled 'error' event
^
Error: spawn cmd ENOENT
at exports._errnoException (util.js:1007:11)
at Process.ChildProcess._handle.onexit (internal/child_process.js:182:32)
at onErrorNT (internal/child_process.js:348:16)
at _combinedTickCallback (internal/process/next_tick.js:74:11)
at process._tickDomainCallback (internal/process/next_tick.js:122:9)
The text was updated successfully, but these errors were encountered: