Closed sanbor closed 7 years ago
Here is the gulpfile that reproduces the bug:
var gulp = require('gulp');
var server = require('gulp-server-livereload');
console.log('wat');
gulp.task('webserver', function() {
console.log('test');
);
This casuses gulp --tasks
to have no output. By commenting the line var server = require('gulp-server-livereload');
then gulp --tasks
starts working as usual.
Same behavior on Windows and Ubuntu. Going back to version 1.5.4 fixes the issue.
Can confirm that my logging changes from the previous version have caused this. Wasn't aware of it at the time, apologies, I will jump on this as soon as I am able.
1.9.1 published with the fix.
I usually use
gulp-server-livereload
on linux but today I tried the project that I'm working on in OSX and I started noticing that gulp doesn't provide any output. Looks like this bug is only affecting OSX for some reason.After some investigation I discover that the line of code that causes this issue is requiring gulp-server-livereload. I was able to reproduce the bug by just doing
var server = require('gulp-server-livereload');
in an almost emptygulpfile.js
, which causes that the commandgulp --tasks
doesn't have any output in the terminal.I commented that line and
gulp --tasks
started working normally.console.log
works ingulpfile.js
, it is just gulp output what is affected.I'm using node 7.0.