fix: require Node.js v24 for create-catalyst, align engine constraints#2940
Merged
chanceaclark merged 4 commits intocanaryfrom Mar 20, 2026
Merged
fix: require Node.js v24 for create-catalyst, align engine constraints#2940chanceaclark merged 4 commits intocanaryfrom
chanceaclark merged 4 commits intocanaryfrom
Conversation
🦋 Changeset detectedLatest commit: 61e47ed The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
… core - Update packages/create-catalyst/package.json engines from ^20.0.0 || ^22.0.0 || ^24.0.0 to ^24.0.0 to match the runtime check in bin/index.cjs and core/package.json (>=24.0.0) - Fix core/README.md which referenced Node.js version 20 or 22 instead of 24 - Extract supported Node.js versions into bin/supported-node-versions.cjs as the single source of truth - Add src/utils/node-version.spec.ts to test the version gating logic Closes #2939 Co-authored-by: chanceaclark <10539418+chanceaclark@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix create-catalyst not working for Node.js v24
fix: align Node.js v24 engine requirements across create-catalyst and core
Mar 20, 2026
Contributor
Bundle Size ReportComparing against baseline from No bundle size changes detected. |
- Use named import { satisfies } from 'semver' instead of default import
(fixes import/no-named-as-default-member warning)
- Remove require() of .cjs file to avoid import/extensions and
@typescript-eslint/consistent-type-assertions errors
- Simplify bin/index.cjs to remove unused intermediate variable
Co-authored-by: chanceaclark <10539418+chanceaclark@users.noreply.github.com>
Contributor
Unlighthouse Performance Comparison — VercelComparing PR preview deployment Unlighthouse scores vs production Unlighthouse scores. Summary ScoreAggregate score across all categories as reported by Unlighthouse.
Category Scores
Core Web Vitals
|
Co-authored-by: chanceaclark <10539418+chanceaclark@users.noreply.github.com>
Copilot
AI
changed the title
fix: align Node.js v24 engine requirements across create-catalyst and core
fix: require Node.js v24 for create-catalyst, align engine constraints
Mar 20, 2026
jorgemoya
approved these changes
Mar 20, 2026
Contributor
|
This PR fixes #2939. |
chanceaclark
added a commit
that referenced
this pull request
Apr 27, 2026
#2940) * Initial plan * fix: align Node.js v24 engine requirements across create-catalyst and core - Update packages/create-catalyst/package.json engines from ^20.0.0 || ^22.0.0 || ^24.0.0 to ^24.0.0 to match the runtime check in bin/index.cjs and core/package.json (>=24.0.0) - Fix core/README.md which referenced Node.js version 20 or 22 instead of 24 - Extract supported Node.js versions into bin/supported-node-versions.cjs as the single source of truth - Add src/utils/node-version.spec.ts to test the version gating logic Closes #2939 Co-authored-by: chanceaclark <10539418+chanceaclark@users.noreply.github.com> * fix: resolve lint errors in node-version.spec.ts - Use named import { satisfies } from 'semver' instead of default import (fixes import/no-named-as-default-member warning) - Remove require() of .cjs file to avoid import/extensions and @typescript-eslint/consistent-type-assertions errors - Simplify bin/index.cjs to remove unused intermediate variable Co-authored-by: chanceaclark <10539418+chanceaclark@users.noreply.github.com> * chore: add changeset for Node.js v24 engine alignment in create-catalyst Co-authored-by: chanceaclark <10539418+chanceaclark@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: chanceaclark <10539418+chanceaclark@users.noreply.github.com>
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
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.
pnpm create @bigcommerce/catalystwas advertising support for Node v20/v22/v24 inpackage.jsonwhile the runtime entrypoint (bin/index.cjs) andcore/package.jsonalready required^24. This mismatch meant users on unsupported Node versions got confusing failures.What/Why?
packages/create-catalyst/package.json—engines.nodenarrowed to^24.0.0to match the runtime gatebin/supported-node-versions.cjs— new file; single source of truth for accepted version ranges, consumed bybin/index.cjscore/README.md— corrected Node.js version reference from "20 or 22" to "24"src/utils/node-version.spec.ts— unit tests asserting v24 is accepted and v18/v20/v22/v23 are rejected.changeset/fix-create-catalyst-node-v24.md— patch changeset for@bigcommerce/create-catalystTesting
pnpm --filter @bigcommerce/create-catalyst testAll version-gating assertions pass: v24.x accepted, v18/v20/v22/v23 rejected.
Migration
Users must be on Node.js v24. This was already the enforced runtime requirement — the
package.jsonenginesfield now makes it explicit at install time.🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.