Making pnpm workspace runs deterministic and patch checks consistent

Written by Alessio on 7/19/2026

Problem

Workspace scripts selected by a regular expression did not guarantee a stable order, and the native install path did not check whether configured patches were still used when creating a fresh lockfile. These gaps made behavior harder to predict and left native and TypeScript installs out of step.

Changes

I restored the --sequential (-s) option for pnpm run, so matched scripts can run with workspace concurrency set to one. Regex-selected script names are sorted lexicographically before execution. In the native install path, I connected unused-patch verification to fresh-lockfile installs and added the allow_unused_patches setting, including tests for filtered installs and warning behavior.

Result

Workspace script execution is predictable when sequential mode is requested, and native installs report unused patches under the same conditions as the TypeScript CLI.

Commits: sequential execution, patch verification