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

Error events.js:72 #5

Open
vdecree opened this issue Jun 3, 2014 · 5 comments
Open

Error events.js:72 #5

vdecree opened this issue Jun 3, 2014 · 5 comments

Comments

@vdecree
Copy link

vdecree commented Jun 3, 2014

Hey there,

This project looks great, just wanted to give it a go. However whenever I run gulp I'm getting:

events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:998:11)
    at Process.ChildProcess._handle.onexit (child_process.js:789:34)

Any ideas?

@davidhund
Copy link
Owner

Thanks Mat,

I can't look into it deeply at the moment but I guess it has something to do with the require('child_process') in jekyll-build and jekyll-watch.

Can you try running one of these tasks alone?

gulp jekyll-watch

See what errors pop up, if any.

It is probably an issue with an incompatible version of Node, Ruby, Sass, etc. Try updating these.

Do you have Ruby (and Sass) installed?
In a similar issue installing/updating Ruby Sass with gem install sass fixed it. See sindresorhus/gulp-ruby-sass#9

@davidhund
Copy link
Owner

Also: see http://stackoverflow.com/questions/21856861/running-jekyll-as-a-child-process-in-gulp-node for possible fixes (if you're on Windows)

@vdecree
Copy link
Author

vdecree commented Jun 3, 2014

Hi David,

I am indeed on windows and I found that last link did the trick. I changed the code to use exec and all seems be working good. Thank for that!

@vdecree
Copy link
Author

vdecree commented Jun 3, 2014

I did also notice when running locally that where you've used markdown such as:

{: .message}

This doesn't appear in browser-sync to work, i just see the markdown syntax and not the output you'd expect. Is this something to do with how i'm viewing it locally?

** edit — after some testing although the exec fixed the errors, the tasks themselves don't appear to run when you use gulp to run everything.

@davidhund
Copy link
Owner

Hey @vdecree

The Grunt/Gulp stuff is a bit of a mess still. I need to clean this up better, apologies.
I'll look into it and see if I can make it run better.

Does it work correctly if you by-pass the Grulp tasks and simply run a jekyll build --config=_config.dev.yml?

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