chore(infra): switch to pnpm 11#28
Draft
Corey-T1000 wants to merge 1 commit into
Draft
Conversation
Migrates package management from npm to pnpm, matching authzed/web which adopted pnpm 11 last week (authzed/web#1508). Changes: - Add `packageManager: "pnpm@11.1.1"` to root package.json - Replace `workspaces` array with pnpm-workspace.yaml - Rewrite root scripts to use `pnpm --filter @authzed/sandworm <task>` instead of `cd sandworm && npm run <task>` - Delete package-lock.json, add pnpm-lock.yaml - Approve native-build packages (sharp, unrs-resolver) used by Next.js Image and ESLint tooling Verified: - `pnpm install` resolves 640 packages clean - `pnpm dev` boots in ~3s (vs ~6s under npm) - Sandworm builds and serves identically Why now: one package manager per monorepo avoids Corepack / lockfile / CI drift. Web is on pnpm; aligning design here keeps them coherent.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
package.jsonaddspackageManagerfield, drops npmworkspacesarray, scripts now usepnpm --filter @authzed/sandworm <task>pnpm-workspace.yamldeclares the sandworm package and approves native-build dependencies (sharpfor Next.js Image,unrs-resolverfor ESLint tooling)package-lock.jsonremoved,pnpm-lock.yamladdedWhy
One package manager per monorepo avoids Corepack / lockfile / CI drift. With web on pnpm and design on npm we'd hit subtle differences (peer-dep resolution, hoisting rules, lockfile semantics) when sharing tooling.
Test plan
pnpm installfrom repo root resolves cleanly (~640 packages)pnpm devboots Sandworm at http://localhost:3000pnpm buildproduces a clean production buildpnpm lintruns Next.js lint without errorspnpminstead ofnpm— flag for reviewerNotes for reviewer
pnpm-workspace.yaml(pnpm 11 requires explicit consent for native postinstalls — security-positive default)^14.1.0; verified working🤖 Generated with Claude Code