Question 1

How do I run a shell command on each file with gulp-exec?

Accepted Answer

Use a function with an ES6 template literal in the exec call, like `exec(file => `command ${file.path}`)`, and pipe it through the Gulp stream as shown in the README example for tasks like git operations or file processing.

Question 2

gulp-exec vs child_process.exec: which should I use?

Accepted Answer

Use gulp-exec when integrating commands into a Gulp file stream; for standalone commands, the README recommends child_process.exec directly to avoid plugin overhead and complexity.

Question 3

How can I make gulp-exec continue on errors?

Accepted Answer

Set the continueOnError option to true in the options object, which prevents the error event from being emitted and allows the pipeline to proceed even if some commands fail.

Question 4

Can gulp-exec run commands in parallel?

Accepted Answer

No, gulp-exec processes files sequentially in the stream; for parallelism, you need to use other Gulp plugins or custom child_process methods, as it's not a built-in feature.

Question 5

How do I upgrade gulp-exec from version 4 to 5?

Accepted Answer

Replace lodash template strings with ES6 template literals in functions, e.g., change `'git checkout <%= file.path %>'` to `file => `git checkout ${file.path}``, as detailed in the upgrading section.

Question 6

Is gulp-exec safe for production with user input?

Accepted Answer

No, avoid using untrusted input in commands due to shell injection risks; always sanitize inputs or use parameterized approaches to mitigate security concerns.

Question 7

How to pipe command output to file contents in gulp-exec?

Accepted Answer

Set pipeStdout to true in the options object, which writes the stdout of the command to file.contents for further processing in the pipeline, as mentioned in the README usage.

gulp-exec

What is gulp-exec?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions