Skip to content

build: convert repo from npm to pnpm - #136

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

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

Conversation

@DylanPiercey

Copy link
Copy Markdown
Contributor

Converts the repo from npm to pnpm (pnpm 11.15.1).

  • Imported package-lock.json into pnpm-lock.yaml via pnpm import (preserves resolved versions) and removed package-lock.json.
  • Added "packageManager": "pnpm@11.15.1" to package.json.
  • Converted npm-isms in scripts: npm ci -> pnpm install --frozen-lockfile, npm i --package-lock-only -> pnpm install --lockfile-only, npm run -> pnpm run.
  • CI: added pnpm/action-setup@v6 before setup-node, cache: pnpm, pnpm install/run; bumped codecov/codecov-action v6 -> v7.
  • Updated husky pre-commit (npm exec lint-staged -> pnpm exec lint-staged), .prettierignore (package-lock.json -> pnpm-lock.yaml), and added lockfile ignores to .gitignore.
  • Release flow uses changesets, which auto-detects pnpm; no workspace: ranges in the manifest so changeset publish is unaffected.

Verification: pnpm install, build (tsc -b && rolldown -c), lint (@ci:lint), and tests (484 passed) all green locally.

@changeset-bot

changeset-bot Bot commented Jul 21, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: c83bc8d

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: 17 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: fa8ae50e-0618-47cf-a600-0547ab8ca7fb

📥 Commits

Reviewing files that changed from the base of the PR and between 295c45b and c83bc8d.

⛔ 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 (5)
  • .github/workflows/ci.yml
  • .gitignore
  • .husky/pre-commit
  • .prettierignore
  • package.json
✨ 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 96.83%. Comparing base (295c45b) to head (c83bc8d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #136   +/-   ##
=======================================
  Coverage   96.83%   96.83%           
=======================================
  Files           8        8           
  Lines         316      316           
  Branches       54       54           
=======================================
  Hits          306      306           
  Misses          4        4           
  Partials        6        6           

☔ 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.

- import package-lock.json into pnpm-lock.yaml (preserves resolved versions), remove package-lock.json
- add packageManager: pnpm@11.15.1 to package.json
- convert npm-isms in scripts (npm ci -> pnpm install --frozen-lockfile, npm i --package-lock-only -> pnpm install --lockfile-only)
- CI: add pnpm/action-setup@v6, cache: pnpm, pnpm install/run; bump codecov-action v6 -> v7
- update husky pre-commit hook, .gitignore, .prettierignore
@DylanPiercey
DylanPiercey force-pushed the dpiercey-ws-pnpm-0rjo9g branch from ccbef17 to c83bc8d Compare July 21, 2026 23:40
@DylanPiercey
DylanPiercey merged commit 2e7c68e into main Jul 22, 2026
11 checks passed
@DylanPiercey
DylanPiercey deleted the dpiercey-ws-pnpm-0rjo9g branch July 22, 2026 00:01
@DylanPiercey DylanPiercey moved this to Done in Roadmap Jul 31, 2026
@DylanPiercey DylanPiercey self-assigned this Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

1 participant