Add pnpm-workspace.yaml to approve dependency build scripts#4
Merged
Conversation
pnpm 11 blocks dependency install/build scripts by default as a supply-chain safeguard. esbuild (downloads its platform binary) and pi-decimals (generates data files) legitimately need theirs, so without approval `pnpm install` exits 1 and `pnpm dev` fails to start. Approve both via allowBuilds so install completes and dev runs.
|
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
pnpm 11 blocks dependency install/build lifecycle scripts by default as a supply-chain safeguard. Two dependencies legitimately need theirs:
postinstalldownloads/links the platform-specific native binaryinstallscript generates required data filesWithout approval,
pnpm installexits with code 1 (ERR_PNPM_IGNORED_BUILDS), and since pnpm 11 verifies dependencies before running a script,pnpm devfails to start on a fresh clone.Change
Adds
pnpm-workspace.yamlapproving both packages viaallowBuilds, so install completes cleanly andpnpm devboots.Testing
pnpm install→ exits 0, both build scripts runpnpm dev→ Next.js dev server ready on http://localhost:3000