gulp has very few flags to know about. All other flags are for tasks to use if needed.
-vor--versionwill display the global and local gulp versions--require <module path>will require a module before running the gulpfile. This is useful for transpilers but also has other applications. You can use multiple--requireflags--gulpfile <gulpfile path>will manually set path of gulpfile. Useful if you have multiple gulpfiles. This will set the CWD to the gulpfile directory as well--cwd <dir path>will manually set the CWD. The search for the gulpfile, as well as the relativity of all requires will be from here-Tor--taskswill display the task dependency tree for the loaded gulpfile--tasks-simplewill display a plaintext list of tasks for the loaded gulpfile--colorwill force gulp and gulp plugins to display colors even when no color support is detected--no-colorwill force gulp and gulp plugins to not display colors even when color support is detected--silentwill disable all gulp logging
The CLI adds process.env.INIT_CWD which is the original cwd it was launched from.
Refer to this StackOverflow link for how to add task specific flags
Tasks can be executed by running gulp <task> <task>....
If more than one task is listed, Gulp will execute all of them concurrently, that is, as if they had all been listed as dependencies of a single task.
Gulp does not serialize tasks listed on the command line. From using
other comparable tools users may expect to execute something like
gulp clean build, with tasks named clean and build. This will not
produce the intended result, as the two tasks will be executed
concurrently.
Just running gulp will execute the task default. If there is no
default task, gulp will error.
You can find a list of supported languages at interpret. If you would like to add support for a new language send pull request/open issues there.