Change in Gulp 4 Task Exposure: Preventing Internal Tasks from Appearing in CLI

Preventing Internal Task Exposure

To hide a task from the Gulp CLI listing, you must avoid registering it with gulp.task() and ensure it is not exported from your gulpfile.js. In Gulp 4, any function registered via the registry or exported as a module member is automatically treated as a public task.

The Solution: Use Unregistered Functions

The most effective way to maintain internal composition tasks while keeping them hidden is to define them as standard JavaScript functions. Because gulp.series() and gulp.parallel() accept function references, they do not require those functions to be registered as Gulp tasks first.

Correct Implementation:

const { series, parallel, src, dest } = require('gulp');

// INTERNAL: Defined as a standard function, NOT registered with gulp.task()
function clean() {
  return src('dist', { read: false, allowEmpty: true }).pipe(someCleanPlugin());
}

// INTERNAL: Another helper function
function compileCss() {
  return src('src/*.css').pipe(someSassPlugin()).pipe(dest('dist'));
}

// PUBLIC: Only this task is registered/exported, making it visible to the CLI
exports.build = series(clean, parallel(compileCss, otherTask));

Why This Works

Gulp 4's CLI scans for tasks in two places: the internal task registry (populated by gulp.task()) and the exports object of your gulpfile. By defining clean and compileCss as local variables/functions, they remain private to the module scope. They are still executable when called by series(), but the CLI has no reference to them as standalone entry points.

Verification Steps

To ensure your internal tasks are successfully hidden, run the following commands in your terminal:

• gulp --tasks: Verify that only your public tasks (e.g., build) appear in the list.
• gulp clean: Attempt to run a hidden task directly. Gulp should return a "task not found" error.

Assumptions and Constraints

This approach assumes you are using Gulp 4.x. If you are using a legacy Gulp 3.x workflow, the registry behaves differently. Note that naming a task with a leading underscore (e.g., _clean) is a convention for developers but provides no actual technical privacy in Gulp 4.

Diagnostic Detail: Are you using a custom task loader or a plugin that automatically scans the directory for files and registers every function it finds as a task? If so, the local function approach may be overridden by the loader.