Skip to content

chore(anchor): set package_manager = pnpm in all Anchor.toml#104

Merged
mikemaccana merged 1 commit into
mainfrom
claude/anchor-package-manager-pnpm
Jul 7, 2026
Merged

chore(anchor): set package_manager = pnpm in all Anchor.toml#104
mikemaccana merged 1 commit into
mainfrom
claude/anchor-package-manager-pnpm

Conversation

@mikemaccana

Copy link
Copy Markdown
Collaborator

Why

Anchor's [toolchain].package_manager was unset in all 54 Anchor.toml files. When unset, Anchor defaults to yarn, which this project's skill bans. The repo already standardises on pnpm (pnpm-lock.yaml at root, mandated in CONTRIBUTING.md), so pnpm — not npm — is the correct value here (the skill's rule is to keep pnpm where a project already uses it).

What

Added to each [toolchain] section:

[toolchain]
# Match the repo package manager (pnpm-lock.yaml at root); avoids Anchor's yarn default.
package_manager = "pnpm"

The programs test via cargo / LiteSVM, so this is mostly latent — but it stops any anchor command that shells out to a JS package manager from picking yarn, and makes the intent explicit. All 54 files validated as parseable TOML.

🤖 Generated with Claude Code


Generated by Claude Code

Anchor's [toolchain] package_manager defaulted to yarn (unset), which the
project's skill bans. The repo already standardises on pnpm (pnpm-lock.yaml at
root, enforced in CONTRIBUTING), so pin pnpm in all 54 Anchor.toml [toolchain]
sections. Programs test via cargo/LiteSVM so this is mostly latent, but it stops
any anchor command that shells out to a JS package manager from picking yarn.
@mikemaccana mikemaccana merged commit 1401b7a into main Jul 7, 2026
38 checks passed
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.

2 participants