| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
✅ Actions performed
Review triggered.
|
Sorry, something went wrong.
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting. Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughMigrate CI and project configuration from Yarn to pnpm and upgrade Node.js targets to 22.x; update package scripts, add a pnpm workspace config, and adjust CONTRIBUTING/README instructions. ChangesPackage Manager and Node.js Migration
Sequence Diagram(s)sequenceDiagram
participant GitHubActions
participant PnpmSetup as pnpm/action-setup@v6
participant SetupNode as actions/setup-node@v4
participant Runner
GitHubActions->>PnpmSetup: install pnpm (version from package.json)
GitHubActions->>SetupNode: configure Node 22.x + cache: pnpm
Runner->>Runner: pnpm install --ignore-scripts
Runner->>Runner: pnpm run lint / pnpm run test -- --coverage / pnpm run build / pnpm run ts:check
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Poem🚥 Pre-merge checks | ✅ 5 ✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches 🧪 Generate unit tests (beta)
Comment @coderabbitai help to get the list of available commands and usage tips. |
Sorry, something went wrong.
| strategy: | ||
| matrix: | ||
| node-version: [18.x] | ||
| node-version: [22.x] |
There was a problem hiding this comment.
Node.js 18 and 20 are EOL
Sorry, something went wrong.
There was a problem hiding this comment.
Switches the project’s development package manager from Yarn Classic to pnpm, updating docs, scripts, CI, and pnpm workspace/security configuration.
Changes:
Copilot reviewed 6 out of 8 changed files in this pull request and generated 4 comments.
Show a summary per file| File | Description |
|---|---|
| README.md | Updates install example from Yarn to pnpm. |
| CONTRIBUTING.md | Updates contributor setup, test, and release commands to pnpm. |
| package.json | Converts scripts to pnpm and pins pnpm/@types/node metadata. |
| pnpm-workspace.yaml | Adds pnpm workspace and security-related settings. |
| pnpm-lock.yaml | Adds pnpm dependency lockfile. |
| yarn.lock | Removes legacy Yarn lockfile. |
| .github/workflows/webpack.yaml | Updates PR CI workflow to Node 22 and pnpm. |
| .github/workflows/coveralls.yaml | Updates coverage workflow to Node 22 and pnpm. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Sorry, something went wrong.
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agentsVerify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. Inline comments: In @.github/workflows/coveralls.yaml: - Line 18: The CI job step using the pnpm/action-setup action (the step that currently references "pnpm/action-setup@v6") should explicitly pin the pnpm version via the action input to avoid the resolution bug; update that workflow step to include a with: version: 11.0.8 (matching devEngines.packageManager) so the action always installs pnpm 11.0.8 instead of relying on the action's bootstrap resolution.
Fix all unresolved CodeRabbit comments on this PR:
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 2015d31c-949c-4022-9627-680b0483090c
📥 CommitsReviewing files that changed from the base of the PR and between f03823a and 2f7e7a9.
📒 Files selected for processing (4)
Sorry, something went wrong.
There was a problem hiding this comment.
In general I'm all good with this.
The single showstopper for me is the pmOnFail issue. If we could just add to the config file:
pmOnFail: download
Then I would be fine with merging this. Even when this gets fixed in pnpm, the old pnpm versions with this issue will still be around for a while, troubling people who would like to check out this library.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
Awesome.
Sorry, something went wrong.
I've upgraded to pnpm 11.9.0 and reverted the workaround here: |
Sorry, something went wrong.
Upgrade to [`pnpm@11.9.0`](https://github.com/pnpm/pnpm/releases/tag/v11.9.0) and remove `pmOnFail: download` workaround: - #949 (review) - my pnpm issue: pnpm/pnpm#11676 - pnpm PR that fixed it: pnpm/pnpm#11682 - pnpm release v11.1.3 that contained the fix: https://github.com/pnpm/pnpm/releases/tag/v11.1.3#:~:text=Fix%20devEngines.packageManager%20(singular%20form%2C%20without%20onFail)%20defaulting%20to%20onFail%3A%20%22error%22%20instead%20of%20the%20documented%20pmOnFail%3A%20%22download%22
| Back | FazBrowse Home | New Git URL |
Switch from yarn@1.22.22 to pnpm@11.0.8, as per #945 (comment).
This also pins @types/node@22.9.0, matching the version previously resolved through yarn.lock. Without the pin, pnpm resolves @types/node@25.6.0, which TypeScript 4.9 cannot check. The observed diagnostics:
Install pnpm via the methods on the installation page:
TODO:
Summary by CodeRabbit
Chores
Documentation