Gulp 4 unhandled stream error pipeline

Unhandled stream error terminates Node process in gulp.src pipeline

0 reputation · 30 Jul 2023, 14:47 UTC

96.2K views0

Goal

Prevent a Gulp 4 pipeline from terminating the Node process when an upstream transform stream emits an error, using one error handler on the pipeline.

Constraints

Stream errors move through the vinyl file system asynchronously, so try/catch cannot capture them. Plugins may swallow or reformat error events, and behavior depends on the plugin and gulp version.

Does an error listener attached only to gulp.dest() protect every upstream stream in the chain, or must each stream handle its own error event? Does the result differ when the pipeline is wrapped in gulp.series()?

1,857 following

Keep exploring this topic

Gulp 4: gulp.lastRun() incremental builds versus full re-runs for large projects

Trade-off between Gulp 4 incremental builds using gulp.lastRun() and full re-runs when non-globbed inputs can change.

Environment-conditional task composition in Gulp 4 pipelines

Gulp 4 pipelines often need environment-specific behavior, but the correct boundary between conditional task composition and in-task stream filtering remains unclear when using series, parallel, and gulp-if.

Gulp 4 parallel task error propagation limits

Gulp 4 requires explicit task completion signals, but the behavior of uncaught stream errors inside gulp.parallel remains unclear: do sibling tasks stop, or do they run until the process exits?

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

Developers want to keep helper tasks that are only used internally in a gulpfile—such as cleanup steps composed with gulp.series or gulp.parallel—from appearing in the output of gulp --tasks or being invocable directly.

Unhandled stream error terminates Node process in gulp.src pipeline

Goal

Constraints

0 answers

Your perspective belongs here.

0 question comments