Skip to content

fix: resolve pnpm catalog: dependencies from pnpm-workspace.yaml - #681

Open
vibgrate-team wants to merge 1 commit into
mainfrom
cursor/pnpm-catalog-deps-e33d
Open

vibgrate-team wants to merge 1 commit into
mainfrom
cursor/pnpm-catalog-deps-e33d

Conversation

@vibgrate-team

Copy link
Copy Markdown
Contributor

Resolves pnpm catalog: dependencies from the root pnpm-workspace.yaml instead of skipping them as non-semver specifiers.

What changed

  • The scanner reads catalog and catalogs once per scan, before registry prefetch.
  • catalog: and catalog:default use the default catalog (top-level catalog, or catalogs.default when that is absent); catalog:<name> uses the named catalog.
  • Drift and lockfile lookup use the resolved specifier; currentSpec keeps the text from package.json.
  • A catalog entry that is an npm: alias follows the existing alias path.
  • A missing catalog entry stays in the scan with an unknown version.

Tests

pnpm test, pnpm lint and pnpm typecheck pass.

Closes #664

Read catalog and catalogs from the root pnpm-workspace.yaml once per scan.
catalog: and catalog:default use the default catalog, and catalog:<name>
uses the named catalog. Drift and lockfile lookup use that specifier,
including an npm: alias stored in the catalog. currentSpec stays as written.
A missing entry remains a row with an unknown version.

Closes #664

Signed-off-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: ABIZ - Agentic Business Record Standard <ops@to.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Enhancement: resolve pnpm catalog: dependencies from pnpm-workspace.yaml

2 participants