Question 1

How to run multiple npm scripts in parallel with redrun?

Accepted Answer

Use the -p flag, for example 'redrun -p lint test build'. This executes the scripts concurrently, and you can combine it with options like --calm for error handling. It's ideal for speeding up CI/CD pipelines or testing suites.

Question 2

Redrun vs npm-run-all: which is faster?

Accepted Answer

Redrun is significantly faster, as shown in the README's speed comparison where redrun completed tasks in 38 seconds compared to 72 seconds for npm-run-all, due to its optimized process management. This makes it better for performance-sensitive workflows.

Question 3

How to set up bash completion for redrun?

Accepted Answer

Run 'redrun-completion >> ~/.bashrc' or 'redrun-completion >> ~/.zshrc' for zsh, then restart your shell. This enables tab-completion for all npm scripts in your package.json, similar to npm's own completion feature.

Question 4

Can redrun be used with Yarn?

Accepted Answer

Redrun is designed for npm scripts, so it may not work directly with Yarn's script runner. If your project uses Yarn but has npm-compatible scripts, it might function, but compatibility isn't guaranteed and could require tweaks.

Question 5

What does the --calm flag do in redrun?

Accepted Answer

The --calm flag makes redrun return a zero exit code even if the script fails, useful for non-critical tasks like linting or formatting where errors shouldn't halt the entire build process. It helps in tolerant error handling scenarios.

Question 6

Is redrun suitable for monorepos?

Accepted Answer

Yes, redrun can handle complex script chains in monorepos by running multiple scripts efficiently in parallel or series. However, ensure all scripts are npm-based and properly nested, as it relies on npm's script definitions for execution.

redrun

What is redrun?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Open Source Alternative To

Frequently Asked Questions