Gulp silently shuts down on task returning empty stream

What were you expecting to happen?

Running gulp all I expect to see:

[15:27:25] Using gulpfile /var/www/project/gulpfile.js
[15:27:25] Starting 'streams'...
[15:27:25] Finished 'streams' after 1.66 ms
[15:27:25] Starting 'dep'...
dep
[15:27:25] Finished 'dep' after 140 μs
[15:27:25] Starting 'all'...
all
[15:27:25] Finished 'all' after 84 μs

What actually happened?

After starting streams task gulp silently exits with code 0:

$ gulp all
[15:28:30] Using gulpfile /var/www/project/gulpfile.js
[15:28:30] Starting 'streams'...
[15:28:30] Starting 'dep'...
dep
[15:28:30] Finished 'dep' after 177 μs
$ echo $?
0

Please post a sample of your gulpfile (preferably reduced to just the bit that’s not working)

gulp.task('dep', function () {
    console.log('dep')
})
gulp.task('streams', function () {
    const streams = require('merge2')()

    return streams
})
gulp.task('all', ['streams', 'dep'], function () {
    console.log('all')
})

What version of gulp are you using? What versions of npm and node are you using?

$ gulp --version
[15:23:48] CLI version 3.9.1
[15:23:48] Local version 3.9.1
$ npm -v
5.2.0
$ node -v
v7.8.0

[phated]

@terinjokes brought up a good point. We already handle this if you are using the separate gulp-cli module. Check out https://medium.com/gulpjs/gulp-sips-command-line-interface-e53411d4467 for more details. (Caveat: you might need gulp 4 to have accurate warning messages).

[phated]

@pattyjung you subscribed to the thread and must unsubscribe yourself, none of us can do that for you…