Repository navigation
pds@0.19.0 fails to install #254
Description
Reproduce
Using create-pds: (resolved to 0.1.0 as of writing)
pnpm dlx create-pds@latest my-pds --yes --pm pnpm --skip-init --skip-git yields
ERR_PNPM_WORKSPACE_PKG_NOT_FOUND In : "@atproto/lex-data@workspace:*" is in the dependencies but no package named "@atproto/lex-data" is present in the workspace
This error happened while installing the dependencies of @getcirrus/pds@0.19.0
at @atproto/space@0.0.0-spaces-alpha-20260818163953
at @atproto/common@0.0.0-spaces-alpha-20261001173819
at @atproto/lex-cbor@0.0.0
Same failure with --pm npm and --pm bun (I only saw the generic failure message for those, so I can't say the cause is identical).
Minimal, without Cirrus at all:
{ "name": "r", "private": true,
"dependencies": { "@atproto/common": "0.0.0-spaces-alpha-20261001173819" } }pnpm install --ignore-scripts
ERR_PNPM_WORKSPACE_PKG_NOT_FOUND "@atproto/lex-data@workspace:*" is in the dependencies but no package named "@atproto/lex-data" is present in the workspace
at @atproto/space@0.0.0-spaces-alpha-20260818163953 (when installing @getcirrus/pds@0.19.0)
at @atproto/common@0.0.0-spaces-alpha-20261001173819
at @atproto/lex-cbor@0.0.0
Claude-generated theorizing:
Cause
@getcirrus/pds@0.19.0 -> @atproto/space@0.0.0-spaces-alpha-20260818163953 -> @atproto/common@^0.0.0-spaces-alpha-20261001173819 -> @atproto/lex-cbor@^0.0.0-spaces-alpha-20261001173819.
Semver says the stable 0.0.0 satisfies ^0.0.0-spaces-alpha-…, so the resolver picks @atproto/lex-cbor@0.0.0 (published 2025-11-24), whose manifest has "@atproto/lex-data": "workspace:*". That can't resolve outside its monorepo. The intended build, @atproto/lex-cbor@0.0.0-spaces-alpha-20261001173819, exists on npm.
Possible fixes
- Upstream (bluesky-social/atproto): use exact versions for the alpha cross-deps, and/or deprecate or unpublish the
0.0.0placeholders. - Cirrus: depend on an
@atproto/spacebuild whose alpha ranges don't resolve to the placeholder, or avoid the alpha dependency chain until it is fixed. A consumer-sidepnpm.overridespin may work around it, but I haven't verified that and wouldn't want to ship alpha builds to a production PDS that way.
Environment: pnpm 10.28.2, Node 26.3.0, macOS. Verified 2026-10-07.
Activity
fix: pin alpha atproto deps so fresh installs resolve (#255)