boxel-cli: publish with pnpm so catalog: deps are resolved#4762
Merged
Conversation
`npm publish` ships the package.json verbatim, leaving the
`catalog:` specifiers in `dependencies` (@aws-crypto/sha256-js,
ignore, jsonwebtoken) untouched in the registry tarball. Any
consumer install fails:
npm: EUNSUPPORTEDPROTOCOL — Unsupported URL Type "catalog:"
pnpm: ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER
— catalog: only resolves inside the publishing workspace
`pnpm publish` rewrites every `catalog:` specifier to its
concrete version from pnpm-workspace.yaml's catalog block before
uploading, producing a tarball that any installer can consume.
This unblocks consumers like boxel-catalog's sync-to-staging
GitHub Action (`npm install -g @cardstack/boxel-cli`), which is
currently broken on every published version of this package.
After merging, cut a new patch release. Existing published
versions on npm are not retroactively fixable; consumers will
need to pin to the new version (or @latest once it is current).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
lukemelia
approved these changes
May 11, 2026
habdelra
approved these changes
May 11, 2026
Contributor
|
we should rev the package in npm after this is merged |
5 tasks
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
3 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.
npm publishships the package.json verbatim, leaving thecatalog:specifiers independencies(@aws-crypto/sha256-js, ignore, jsonwebtoken) untouched in the registry tarball. Any consumer install fails:npm: EUNSUPPORTEDPROTOCOL — Unsupported URL Type "catalog:"
pnpm: ERR_PNPM_SPEC_NOT_SUPPORTED_BY_ANY_RESOLVER
— catalog: only resolves inside the publishing workspace
pnpm publishrewrites everycatalog:specifier to its concrete version from pnpm-workspace.yaml's catalog block before uploading, producing a tarball that any installer can consume.This unblocks consumers like boxel-catalog's sync-to-staging GitHub Action (
npm install -g @cardstack/boxel-cli), which is currently broken on every published version of this package.After merging, cut a new patch release. Existing published versions on npm are not retroactively fixable; consumers will need to pin to the new version (or @latest once it is current).