-
-
Notifications
You must be signed in to change notification settings - Fork 80.7k
[Bug]: pnpm install fails out-of-the-box on standard Node v22 LTS (v22.17.0) #97792
Copy link
Copy link
Closed
Closed
Copy link
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.ClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.Good issue quality with a plausible reproduction path needing some confirmation.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.Issue affects a taxonomy feature currently scored M4/M5.no-staleExclude from stale automationExclude from stale automation
Description
Metadata
Metadata
Assignees
Labels
P2Normal backlog priority with limited blast radius.Normal backlog priority with limited blast radius.clawsweeper:fix-shape-clearClawSweeper found a clear likely implementation shape for this issue.ClawSweeper found a clear likely implementation shape for this issue.clawsweeper:needs-live-reproClawSweeper needs live local, crabbox, or manual validation to confirm this issue.ClawSweeper needs live local, crabbox, or manual validation to confirm this issue.clawsweeper:queueable-fixClawSweeper marked this issue as an existing queue_fix_pr work candidate.ClawSweeper marked this issue as an existing queue_fix_pr work candidate.impact:otherThis issue has meaningful maintainer-visible impact outside the owned taxonomy.This issue has meaningful maintainer-visible impact outside the owned taxonomy.issue-rating: 🐚 platinum hermitGood issue quality with a plausible reproduction path needing some confirmation.Good issue quality with a plausible reproduction path needing some confirmation.maturity:stableIssue affects a taxonomy feature currently scored M4/M5.Issue affects a taxonomy feature currently scored M4/M5.no-staleExclude from stale automationExclude from stale automation
Type
Fields
Priority
None yet
What Problem This Solves
New contributors cloning the repository and running pnpm install on a standard LTS version of Node (e.g., �22.17.0) encounter a hard installation failure because the package.json strict engine requirement is set to {node:>=22.19.0}. This creates an immediate friction point for onboarding contributors.
Expected vs Actual Behavior
Expected: pnpm install should succeed on the current active Node v22 LTS branch, or the documentation/scripts should gracefully handle the minor version gap without failing the entire install process.
Actual: The installation fails with: [WARN] Unsupported engine: wanted: {node:>=22.19.0} (current: {node:v22.17.0,pnpm:11.2.2}), blocking all subsequent commands like pnpm run lint or pnpm test.
Proposed Solution
Evaluate if >=22.19.0 is strictly necessary for a specific Node feature. If not, downgrade the requirement in package.json to >=22.17.0. Alternatively, if it is required, update CONTRIBUTING.md to explicitly state the minor version requirement and recommend
vm or nm.