build: switch the dev workflow from npm to pnpm#5
Merged
jamoy merged 1 commit intoJun 22, 2026
Merged
Conversation
- pin pnpm via the `packageManager` field (Corepack) and commit pnpm-lock.yaml (replacing package-lock.json) - move the dependency `overrides` to `pnpm.overrides` (pnpm doesn't read npm's top-level overrides), keeping `npm audit` / `pnpm audit` at 0 advisories - add .npmrc `auto-install-peers=false` so the optional `serverless` peer (and its large tree) is not pulled into the dev install, matching npm's behavior - acknowledge jest's optional native resolver (unrs-resolver) as an ignored build dependency; jest uses its JS fallback, which keeps installs robust on brand-new Node releases - CI: install pnpm via pnpm/action-setup, cache the pnpm store, and run `pnpm install --frozen-lockfile` + pnpm lint/test/test:smoke - husky pre-commit now runs `pnpm exec lint-staged` - README: document pnpm install/usage Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QznGWnSQuwvNRAcYinsZiG
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
1 participant
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.
Stacked on #4 (which is stacked on #3) — review/merge those first; this PR's diff is only the pnpm migration on top.
Switches the repo's development workflow from npm to pnpm, with no change to the published package contents or its public API.
What changed
packageManagerfield (Corepack):pnpm@10.33.0.package-lock.json→pnpm-lock.yaml(committed for reproducible installs).overridestopnpm.overrides(pnpm ignores the former). Theunderscore/js-yamlpins still apply, sopnpm auditreports 0 vulnerabilities..npmrcwithauto-install-peers=falseso pnpm doesn't pull the optionalserverlesspeer (and its large tree) — matching npm's behavior.unrs-resolveras an ignored build dependency. Jest uses its JS fallback, so installs stay robust on brand-new Node releases (no native build required).pnpm/action-setup@v4, caches the pnpm store throughactions/setup-node(cache: pnpm), and runspnpm install --frozen-lockfile+pnpm lint/pnpm test/pnpm test:smoke.pnpm exec lint-staged.Verified locally with pnpm 10.33.0
pnpm install --frozen-lockfile✓pnpm test→ 88 passing, 5 skipped ✓pnpm lint(ESLint + Prettier) ✓pnpm test:smoke(dual ESM/CJS) ✓pnpm audit→ no known vulnerabilities ✓🤖 Generated with Claude Code
https://claude.ai/code/session_01QznGWnSQuwvNRAcYinsZiG
Generated by Claude Code