Home » Nodejs » Running jekyll as a child process in Gulp/Node

Running jekyll as a child process in Gulp/Node

Posted by: admin November 29, 2017 Leave a comment

Questions:

I’m trying to build a jekyll site using Gulp.js. I’ve read that I shouldn’t use a plugin in this question.

I’ve been investigating using a child process as suggested but I keep getting an error:

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

Here’s my gulp file:

var gulp = require('gulp');
var spawn = require('child_process').spawn;
var gutil = require('gulp-util');

gulp.task('jekyll', function (){
    spawn('jekyll', ['build'], {stdio: 'inherit'});
});

gulp.task('default', ['jekyll']);

What am I doing wrong? I’m on Node 0.10.25, Win 7.

EDIT
I’ve had a google around ENOENT errors previously. Have checked my path and Ruby is there and I can run jekyll from the command line. Still no joy.

Answers:

I also had this problem and found the answer to using spawn.

The problem is with how Node finds executables on Windows. For more details look at this answer:

https://stackoverflow.com/a/17537559

In short, change spawn('jekyll', ['build']) to spawn('jekyll.bat', ['build']) in order to get spawn to work.

Questions:
Answers:

So I ended up using exec instead. Here’s my gulp file:

var gulp = require('gulp');
var exec = require('child_process').exec;
var gutil = require('gulp-util');

gulp.task('jekyll', function (){
exec('jekyll build', function(err, stdout, stderr) {
    console.log(stdout);
});
});

Here’s a post about the differences