GeezerVison

Why: pnpm can already do what npm-run-all2 does, so it's one less dev dependency (~17 packages in its tree). run-s a b becomes pnpm run a && pnpm run b. run-p a b becomes a regex selector (pnpm run "/^build:(transpile|types)$/"), which runs the matching scripts of the current package concurrently and exits non-zero (killing the rest) when one fails. The 51 run-p/run-s calls that wrapped a single script are now plain pnpm run x.

Non-obvious choices:

• No --parallel. It makes pnpm run recursive, and in a package dir it started the watch scripts of all 63 workspace projects.
• Regex selectors run at most as many scripts at once as there are CPUs (capped at 4), while run-p had no cap. Builds keep that CPU-bound default. The 6 *:watch combos pass --workspace-concurrency=Infinity, because on one core the second long-running watcher would never start. Checked with taskset -c 0.

How to review: The diff was generated mechanically (a script checked that every referenced script exists). Skim the root package.json and one watch script, e.g. packages/browser.

Unsure about: Four e2e test apps (vue-3, vue-3-static, react-router-6*) still list npm-run-all2 as their own dependency. They're standalone fixture apps (the Vue ones are create-vue scaffolds using {@} arg forwarding), so I left them alone.

Verified locally: pnpm run verify (format + lint), the core build, the vue sequential build:types chain, browser build:watch on 1 CPU (both watchers start, nothing outside the package runs), and pnpm install dropping npm-run-all2 from the lockfile.

via @mydea.

--

View Session [Sentry]