fix(workspace): add packages field so pnpm prepare succeeds

pnpm-workspace.yaml carried only allowBuilds, with no packages field.
Recent pnpm rejects this with ERR_PNPM_INVALID_WORKSPACE_CONFIGURATION
("packages field missing or empty") during the prepare step it runs
inside any consumer that pulls @openclaw/fs-safe from a github tarball,
breaking installs in downstream repos that pin a commit (e.g. openclaw).

Adding packages: [] keeps the file a valid (empty) workspace root while
preserving the allowBuilds: { esbuild: true } directive. Verified by
extracting the working tree to a clean directory and running
pnpm install -- which now completes without error.
This commit is contained in:
Sarah Fortune 2026-05-06 16:33:34 -07:00
parent 85f5b55050
commit 2a3db08b8d

View File

@ -1,2 +1,4 @@
packages: []
allowBuilds:
esbuild: true