gulp-jekyll
gulp-jekyll copied to clipboard
unhandled stream error in pipe
Setup the plugin per your example, but getting an unhandled stream error. Error code 10.
I faced the same problem here when jekyll logs some waring during the template generation.
Didn't have time to debug, so I'm just guessing for the reason. Have you installed Jekyll? From the code.
'You need to have Ruby and Jekyll installed and in your PATH for this task to work.'
I do have jekyll installed. I am pretty sure the error would return that line if Jekyll wasn't installed?
I got the exact same error, any ideas?
i got the same error too
maybe I can add some additional context:
[gulp] Finished 'blog' after 5.94 ms
stream.js:94
throw er; // Unhandled stream error in pipe.
^
[gulp] Error in plugin 'gulp-jekyll':
Configuration file: none
Liquid Exception: invalid byte sequence in UTF-8 in node_modules/connect/node_modules/multiparty/test/fixture/multi_video.upload
error: invalid byte sequence in UTF-8. Use --trace to view backtrace
at ChildProcess.<anonymous> (/Users/vince/Projects/vinspee.me/node_modules/gulp-jekyll/index.js:45:15)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:743:16)
at Socket.<anonymous> (child_process.js:956:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:465:12)
it seems like the issue is actually being thrown fron jekyll.
I'm getting a similar error. I'm running Win7x64 with and Ruby 2.0.0-p451. Jekyll 1.4.3 definitely has a separate issue with serving and watching files that's supposed to be fixed in the 2.0 release, so for now we have to downgrade to 1.4.2. At this point, you should be able to jekyll serve --watch
just fine (not involving gulp at this point yet).
If I gulp
now I get this:
stream.js:94
throw er; // Unhandled stream error in pipe.
^
[←[32mgulp←[39m] Error in plugin '←[36mgulp-jekyll←[39m':
DL is deprecated, please use Fiddle
at ChildProcess.<anonymous> (D:\projects\cmegown.github.io\node_modules\gulp-jekyll\index.js:45:
15)
at ChildProcess.EventEmitter.emit (events.js:98:17)
at maybeClose (child_process.js:735:16)
at Socket.<anonymous> (child_process.js:948:11)
at Socket.EventEmitter.emit (events.js:95:17)
at Pipe.close (net.js:466:12)
I'm no Ruby pro by any means, but from my searching I think this has something to do with a readline
deprecation. I've commented out the warning on line 8 in dl.rb
, but now I'm getting a new error when running gulp
.
Exited with error code 10
No luck running this under Jekyll 2.0.2. Has anyone had any success?
This looks like the same issue as here: https://github.com/shakyShane/grunt-browser-sync/issues/25
Adding 'node_modules'
into the exclude:
within jekyll's config.yml
ought to fix it
@oller yes and no
The solution is to provide any jekyll config e.g.
encoding: utf-8
Because if not, this line throws a warning: https://github.com/jekyll/jekyll/blob/master/lib/jekyll/configuration.rb#L164
and is catched by this lines: https://github.com/dannygarcia/gulp-jekyll/blob/develop/index.js#L44-L46
SOLUTION: provide a jekyll config with just any default param
pity that this project is not maintained @dannygarcia (want to give some dev rights to someone?)
More than happy to grant someone else rights to maintain this repo.
On Oct 1, 2014, at 7:59 AM, Robin Böhm [email protected] wrote:
@oller yes and no
The solution is to provide any jekyll config e.g.
encoding: utf-8 Because if not, this line throws a warning: https://github.com/jekyll/jekyll/blob/master/lib/jekyll/configuration.rb#L164
and is catched by this lines: https://github.com/dannygarcia/gulp-jekyll/blob/develop/index.js#L44-L46
SOLUTION: provide a jekyll config with just any default param
pity that this project is not maintained @dannygarcia (want to give some dev rights to someone?)
— Reply to this email directly or view it on GitHub.
I was getting this error too, but then I found stack overflow post that lead me to write this:
gulp.task('build', function (cb) {
var build = require('child_process').spawn('jekyll', ['build'], {stdio: 'inherit'});
build.on('exit', cb);
});
You don't really need a plugin.
See also this post, linked to from the Gulp GitHub project.