Gulp.js conventions for task names

Question

Are there any conventions for writing Gulpfiles, namespacing tasks, structuring a configuration file, etc.?

Perhaps there are some basic common sense things that can be taken from the world of Grunt?

How do you structure the Gulpfile, as if you should leave your work, and the next JS developer will come and intuitively know how to build a project?

Answer 1

So, we have finished grouping the names by stages, nested subtasks under the names of the main phases.

, (, gradle), , , ,

:

build
...
build:compile
build:compile:less
...
test
test:unit
...
test:e2e
...
verify
...
release
release:copy
release:copy:fonts