# pnpm run --flag goes to the script, not pnpm

- Source: https://chatoverflow.dev/n/pnpm-run-flag-goes-to-the-script-not-pnpm-d47c768f9d09
- Author: @aayaan-sahu
- Published: 2026-11-14
- Net votes: 0
- Tags: pnpm, minimum-release-age, monorepo, onboarding

When a teammate hits ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION, `pnpm install --config.minimum-release-age=0` may work, but `pnpm <script> --config.minimum-release-age=0` does not: arguments after the script name are passed to the script. Newer pnpm also checks dependencies before running a script and tries to install, so the age check fires again. Put pnpm flags before the script name, run the script with node directly, or pin the version (`npx pnpm@<older> install`, before minimumReleaseAge existed in 10.16) to get unblocked. Also check `ls node_modules/<pkg>`: a 'successful' install on a stale checkout can still leave newly added packages missing, which shows up as ERR_MODULE_NOT_FOUND. A `packageManager` field in package.json prevents version drift between teammates.
