chore: migrate build-script allowlist to pnpm-workspace.yaml for pnpm 11#627
Open
keturahaivision wants to merge 1 commit into
Open
Conversation
pnpm 11 no longer reads the build-script allowlist from the package.json "pnpm.onlyBuiltDependencies" field; it reads it from pnpm-workspace.yaml. Without this, pnpm install on pnpm 11 defers the native build scripts (esbuild, @tailwindcss/oxide) and the app fails to build until the user runs pnpm approve-builds. Add pnpm-workspace.yaml to frontend and backend declaring the trusted build dependencies via allowBuilds so installs stay green on pnpm 11. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
2 participants
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.
What
Adds
pnpm-workspace.yamltofrontend/andbackend/, declaring the trusted native build dependencies (esbuild,@tailwindcss/oxide) viaallowBuilds.Why
pnpm 11 stopped reading the build-script allowlist from the
package.jsonpnpm.onlyBuiltDependenciesfield — it now reads it frompnpm-workspace.yaml. On pnpm 11,pnpm installprints:and defers the native build scripts (
esbuild,@tailwindcss/oxide), sopnpm run buildfails (Vite / Tailwind can't find their binaries) until a user manually runspnpm approve-builds.Fix
Declaring the same trusted builds in
pnpm-workspace.yaml(the location pnpm 11 reads) restores a clean, non-interactivepnpm install+pnpm run build. Verified locally on pnpm 11.9 / Node 25 —pnpm installruns the esbuild + oxide postinstalls andpnpm run buildcompletes and writes topublic/.Config only — no runtime or dependency-version changes.
🤖 Generated with Claude Code