ERR_PNPM_PEER_DEP_ISSUES during CI install: enforce strict peer checks or bypass them in a monorepo?
In a pnpm monorepo (workspace with several child packages, pnpm v8 assumed), the install step in CI aborts with ERR_PNPM_PEER_DEP_ISSUES , reporting unmet peer dependencies for a shared library consumed by multiple workspace packages. The deployment pipeline fails at this point, and the lockfile is committed and up to date. The unresolved decision is how to