`npm-run-all2` is a command-line interface (CLI) tool designed to efficiently manage and execute multiple npm scripts. It enables running scripts concurrently in parallel or in a specified sequence, offering fine-grained control over complex build or development workflows. As a maintenance fork of the popular `npm-run-all` package, its primary focus is on ongoing maintenance, modernizing the codebase, and ensuring compatibility with recent Node.js versions. As of its current stable version 8.0.4, it specifically requires Node.js 20 or greater. It maintains a consistent release cadence, frequently incorporating updates and addressing compatibility concerns. Its key differentiator is its commitment to supporting contemporary Node.js environments and acting as a well-maintained alternative to its predecessor, particularly for projects that require updated dependencies or strict Node.js versioning.
npm install npm-run-all2Verified import paths — ran on the pinned version, not inferred.
Demonstrates `npm-run-all2` for parallel and sequential execution of npm scripts, including glob patterns, in a typical project setup.
Upgrade your Node.js environment to version `20.5.0` or higher.
Refactor programmatic imports from CommonJS `require()` to ESM `import { /* ... */ } from 'npm-run-all2'`.Upgrade to `8.0.3` or higher to ensure consistent `minimatch` glob behavior.
Explicitly install `npm-run-all2` (e.g., `npm install --save-dev npm-run-all2`) and ensure your `package.json` scripts call `npm-run-all2` instead of `npm-run-all`.
Upgrade your Node.js environment to version `20.5.0` or higher (e.g., using `nvm install 20 && nvm use 20`).
Install `npm-run-all2` locally as a `devDependency` (`npm install --save-dev npm-run-all2`) and ensure it's called via `npm run <script>` (which uses `node_modules/.bin`), or install it globally (`npm install -g npm-run-all2`) if you intend to use it directly from the terminal.
Refactor your code to use ESM `import` statements (e.g., `import { runAll } from 'npm-run-all2';`).Verify the script names in `package.json` and adjust the glob pattern accordingly. For `v8.0.2`, consider upgrading to `v8.0.3+` to revert to `minimatch` glob behavior.
No dependency data recorded yet.