In gulp --tasks, we should be able to list only "public" tasks.

[kud]

I love to simplify things and hiding private gulp tasks could be great. Some tasks alone have no sens for the end user. Only display public tasks.

Something like https://www.npmjs.org/package/gulp-task-listing could be great.

[sindresorhus]

Yes, gulp should somehow have a notion of public and private tasks.

[heikki]

Isn't that coming in version 4 with "private task" being just a function? .. or do I remember plans correctly ..

[yocontra]

Use functions and don't register them with gulp.task

[kud]

Thanks :)

[sindresorhus]

@contra but then you lose out on the dependency and concurrency stuff.

[kud]

Oh, so please reopen the issue. :)

[yocontra]

@robrich adding support for a fn instead of a task name in a deps array?

[robrich]

Interesting idea, but in gulp 4, there is no dependency array.

[nodesocket]

I'd like to see a way to define tasks as internal as well. Since I use:

gulp.task('build', function(cb) {
    runSequence('uglify', 'buildHTML', 'rmRevManifest', cb);
}

Tasks uglify, buildHTML, and rmRevManifest don't need to be exposed publicly.

Perhaps a new function?

gulp.internalTask()

[yocontra]

Please see the new task system spec before commenting about new ideas - the new task system is different and has a different goal.

[pkozlowski-opensource]

@contra I might be late to the party, but where I can actually find spec for the "new task system" - would be very interested in having a look but couldn't find references to the mentioned docs in the README nor on WIKI pages. Googling didn't bring any relevant results either...

[Delapouite]

@pkozlowski-opensource : #355 (comment)

[pkozlowski-opensource]

I believe that this issue should be closed in favour of #355 where a new task system is discussed. With the proposed approach one can use any async function as part of task dependencies. Personally I think that ideas behind the proposal in #355 are (very) solid (there are just few things to sort out left) and a new task system is going to solve this issue (plus some others) in the very elegant way.

[yocontra]

@phated How will this be supported in gulp 4?

[phated]

In gulp4, you don't register a function with gulp.task. anonymous functions will show up as <anonymous> in the output and named functions will show up as <FUNCTION_NAME>, which allows us to display series/parallel names.

[kud]

Niiiice. :)

[yocontra]

Closing this since it already exists in 4.0