Skip to content

build: convert repo from npm to pnpm#232

Merged
DylanPiercey merged 1 commit into
mainfrom
dpiercey-ws-pnpm-0rjo9g
Jul 21, 2026
Merged

build: convert repo from npm to pnpm#232
DylanPiercey merged 1 commit into
mainfrom
dpiercey-ws-pnpm-0rjo9g

Conversation

@DylanPiercey

Copy link
Copy Markdown
Contributor

Converts the repo from npm to pnpm 11.

  • Lockfile imported via pnpm import (resolved versions preserved); package-lock.json removed.
  • packageManager: pnpm@11.15.1 pinned; pnpm-workspace.yaml added with allowBuilds: { esbuild: true } so esbuild's postinstall runs (pnpm 11 blocks build scripts by default).
  • package.json scripts: npm-isms converted (npm run -> pnpm run, npm i --package-lock-only -> pnpm install --lockfile-only in the changesets version script).
  • CI: pnpm/action-setup@v6 added before setup-node, cache: pnpm, pnpm install --frozen-lockfile; codecov-action bumped v5 -> v7.
  • Husky pre-commit: npx --no-install lint-staged -> pnpm exec lint-staged.
  • Ignore files updated (pnpm-lock.yaml in .prettierignore; package-lock.json/yarn.lock gitignored).

Release flow: changesets auto-detects pnpm for publish; version/release scripts updated accordingly.

Verification: clean pnpm install --frozen-lockfile, pnpm run build, pnpm run lint, and pnpm test all pass locally.

- import package-lock.json to pnpm-lock.yaml (resolved versions preserved) and remove package-lock.json
- add packageManager: pnpm@11.15.1 and pnpm-workspace.yaml (allowBuilds: esbuild for its postinstall)
- convert npm-isms in package.json scripts to pnpm equivalents
- CI: add pnpm/action-setup@v6, cache pnpm, pnpm install --frozen-lockfile, pnpm run; bump codecov-action to v7
- husky pre-commit: npx lint-staged -> pnpm exec lint-staged
- ignore files: prettierignore pnpm-lock.yaml; gitignore package-lock.json and yarn.lock
@changeset-bot

changeset-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: cf73c16

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai

coderabbitai Bot commented Jul 21, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 23 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 525448dd-bed7-4b06-83e6-4c92295d0362

📥 Commits

Reviewing files that changed from the base of the PR and between 93850d2 and cf73c16.

⛔ Files ignored due to path filters (2)
  • package-lock.json is excluded by !**/package-lock.json and included by **
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml and included by **
📒 Files selected for processing (6)
  • .github/workflows/ci.yml
  • .gitignore
  • .husky/pre-commit
  • .prettierignore
  • package.json
  • pnpm-workspace.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dpiercey-ws-pnpm-0rjo9g

Comment @coderabbitai help to get the list of available commands.

@codecov

codecov Bot commented Jul 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.95%. Comparing base (93850d2) to head (cf73c16).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #232   +/-   ##
=======================================
  Coverage   99.95%   99.95%           
=======================================
  Files          34       34           
  Lines        4270     4270           
  Branches      793      793           
=======================================
  Hits         4268     4268           
  Misses          2        2           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@DylanPiercey
DylanPiercey merged commit 3819faa into main Jul 21, 2026
11 checks passed
@DylanPiercey
DylanPiercey deleted the dpiercey-ws-pnpm-0rjo9g branch July 21, 2026 23:38
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.

1 participant