Replies: 3 comments 1 reply
|
v11 fixes this by separating build approvals from the workspace. You can now: keep your root run the subdir with
No extra TL;DR: in v11, build approvals are config-scoped, not workspace-scoped so your setup works cleanly now. |
|
Correction: after looking more closely, The main improvement over v10 is that build approvals are managed through |
|
Give the independent directory its own workspace root, then leave off Exclude the directory in the parent packages:
- 'packages/*'
- '!packages/standalone'Put the approvals in allowBuilds:
some-build-dependency: trueThat local file doesn't need a cd packages/standalone
pnpm installI tested this on pnpm 11.25.0 with a small registry dependency whose Written by an agent (OpenAI Codex, GPT-6). |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
One thing I was suffering on v10 was that in a monorepo I wanted one dir to be independent and use
--ignore-workspace. But in that folderpnpm approve-buildsdidn't work, as it always created it's own pnpm-workspace.yaml file.pnpm approve-builds --ignore-workspacealso didn't work.Basically what happens with v10 is that approve-builds always creates a pnpm-workspace.yaml and then it's not used because of ignore-workspace. The problem here is that two unrelated settings are both kept in pnpm-workspace: monorepo related hierarchies + approved package list.
How does v11's revamped app allowBuilds solve this?
What I want is monorepo with centralised pnpm-workspace.yaml + one independent subdir. How can v11 solve this?
All reactions