Migrate pnpm config to v11#88
Conversation
WalkthroughThis PR upgrades pnpm from version 10.30.0 to 11.6.0 across the workspace by updating the 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@examples/next-smoke/pnpm-workspace.yaml`:
- Around line 4-5: Confirm that the workspace override syntax in
pnpm-workspace.yaml is correct for pnpm v11 (the overrides.postcss key is valid)
and update the file or PR description to include a short rationale for pinning
postcss to 8.5.10 (e.g., compatibility with Next.js/other deps, security fixes,
or reproducible installs) and mention that pnpm-lock.yaml currently resolves
postcss to 8.5.10 (so this is not a downgrade from 8.5.15).
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 21936d78-b3e0-4ee7-b9ad-ee95aebb6b15
📒 Files selected for processing (4)
examples/hello-world/package.jsonexamples/next-smoke/package.jsonexamples/next-smoke/pnpm-workspace.yamlpackage.json
Updates the repository pnpm configuration for pnpm v11 compatibility after the package-manager pin moved from v10 to v11.
Changes
pnpm@11.6.0so local and example installs do not fall back to pnpm 10..node-versionto the latest Node 22 release and raises the root development engine floor to>=22.13.0, matching pnpm v11's runtime requirement.postcssoverride out of the removedpackage.json#pnpmconfig field and intoexamples/next-smoke/pnpm-workspace.yaml, where pnpm v11 reads project configuration. The8.5.10pin preserves the existing lockfile resolution, so this migration does not downgrade the example from a newer PostCSS release.allowBuilds.esbuild: trueto the root and standalone example workspaces so esbuild install scripts are explicitly approved under pnpm v11's build policy.Why
pnpm v11 no longer reads pnpm-specific settings from the
pnpmfield inpackage.json, requires Node>=22.13, and usesallowBuildsfor dependency build-script approvals. Keeping these settings in workspace config preserves the existing install behavior while making the repo compatible with v11.