-
Notifications
You must be signed in to change notification settings - Fork 56
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
Nodejs 0.10 events.js exception #30
Comments
Do you have Pygments installed? That's one possible cause of that error - check out http://pygments.org/download/ if not. In other news, I am planning to drop the pygments dependency very soon, as soon as I can find the time. |
Ah it's working now. Maybe you could add a check in your code to detect it and give an informative error message. In a project I'm using this:
|
Yeah that'd be a good idea. I think I put something in the npm install script, but yeah probably should have something in the actual runner too. |
I'm going to close this as I've already got #31 open for dropping the pygments dependency ASAP. Doing a "which pygmentize" probably wouldn't be suitable as a sanity check because it wouldn't work on windows machines. I think for now I'm just going to leave it and hopefully rip out the pygments dependency altogether very soon. |
Hi jbt. I just recently discovered shelljs. This is a portable posix shell interface for node. It has a "which" method that should work on Windows too as I understand it. But it adds a dependency of course... |
I'm just trying out docker for the first time, but I keep getting this exception no matter what I try. I just upgraded to node 0.10, maybe it's not compatible?
events.js:72
throw er; // Unhandled 'error' event
^
Error: spawn ENOENT
at errnoException (child_process.js:945:11)
at Process.ChildProcess._handle.onexit (child_process.js:736:34)
The text was updated successfully, but these errors were encountered: