You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(core): don't check the Node.js version on the Bun runtime - #13024
The Docusaurus CLI refuses to run on the Bun runtime (bun --bun docusaurus …): Bun 1.4.4 reports process.version as v26.12.1, below our >=26.13 engine, and the CLI exits with "Minimum Node.js version not met".
Our >=26.13 requirement is the Node.js LTS floor (#12821), not a Node.js API we need, and the Node.js version that Bun reports doesn't tell which Node.js APIs it implements. So we skip this check on Bun.
Running bun run start without --bun isn't affected: the CLI shebang runs it with Node.js.
Review was skipped as selected files did not have any reviewable changes.
Run configuration
Source mode: Auto
Repository: Unavailable
Branch: Unavailable
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: 7dbb2c6c-4e54-423d-a7cd-c6d27e884fcf
Commits
Reviewing files that changed from the base of the PR and between 49566e1 and 49566e1.
You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.
Use the checkbox below for a quick retry:
Trigger review
No actionable comments were generated in the recent review.
Walkthrough
beforeCli now skips the Node.js version requirement check when Bun is running. Other runtimes continue to be checked against requiredVersion, with the existing error and exit behavior on mismatch.
Changes: Bun Runtime Version Check
Layer / File(s)
Summary
Runtime detection and version validation packages/docusaurus/bin/beforeCli.mjs
beforeCli detects Bun and bypasses the Node.js version check. Other runtimes retain the existing version validation and failure behavior.
meta/docusaurus#12821: This PR sets the Node.js version requirement that Bun’s reported version does not meet.
meta/docusaurus#13022: This PR adds the Bun CI job that encounters the version check failure.
Merge Risk: Minimal · up to 49566
Docusaurus can now run under the Bun runtime without being rejected by the Node.js version check. Other runtimes are still checked as before, so there is no identified merge-blocking risk.
Pre-merge checks: 4
Check name
Status
Explanation
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Title check
The title names the main change: the CLI no longer checks the Node.js version when running on the Bun runtime. The raw summary confirms that beforeCli.mjs detects Bun through process.versions.bun and …
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Title check
Explanation
The title names the main change: the CLI no longer checks the Node.js version when running on the Bun runtime. The raw summary confirms that beforeCli.mjs detects Bun through process.versions.bun and skips the Node.js version check under Bun, while other runtimes are still checked. The title is specific and matches the changeset and the PR objectives.
Finishing Touches
Generate unit tests (beta)
Commit to this branch
Create a new PR
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: defaults
Review profile: CHILL
Plan: Advanced
Run ID: 8ceaa739-2866-4d7f-9d1b-f3d90565f12d
Commits
Reviewing files that changed from the base of the PR and between 56d119e and 49566e1.
Files selected for processing: 1
packages/docusaurus/bin/beforeCli.mjs
Included review availability: This review used your included allowance. Your plan provides up to 10 included reviews per hour; 8 remain after this review.
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
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.
Motivation
The Docusaurus CLI refuses to run on the Bun runtime (
bun --bun docusaurus …): Bun 1.4.4 reportsprocess.versionasv26.12.1, below our>=26.13engine, and the CLI exits with "Minimum Node.js version not met".Our
>=26.13requirement is the Node.js LTS floor (#12821), not a Node.js API we need, and the Node.js version that Bun reports doesn't tell which Node.js APIs it implements. So we skip this check on Bun.Running
bun run startwithout--bunisn't affected: the CLI shebang runs it with Node.js.Test Plan
E2E — Bunjob added by ci: add a Bun E2E job #13022, failing there, should pass on this PR.bun --bun docusaurus --version,startandbuildwork on the website and on a new classic site.Test links
Deploy preview: https://deploy-preview-13024--docusaurus-2.netlify.app/
Related issues/PRs
Stacked on #13022
🤖 Generated with Claude Code
Summary by CodeRabbit