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(utils): reload the modules imported by the config on the Bun runtime - #13026
With docusaurus start on the Bun runtime, editing docusaurus.config.ts reloads the config, but not the modules it imports: they keep their old values until the dev server restarts. The same goes for sidebars and plugins loaded with loadFreshModule().
jiti defaults to tryNative: "Bun" in globalThis: on Bun, it loads modules with the native import(), whose module cache lives as long as the process. Our moduleCache: false option doesn't bypass it. With tryNative: false, jiti uses its own loader on Bun too, like on Node.js.
The bunosaurus fork found and fixed the same problem.
Test Plan
Vitest runs on Node.js, so I tested it manually on a new classic site whose docusaurus.config.ts imports tagline from a siteTagline.ts module. I ran docusaurus start, changed siteTagline.ts, then edited the config to trigger a reload, and checked .docusaurus/docusaurus.config.mjs:
This change makes edited config, sidebar and plugin modules reload on Bun during development. No concrete regression was established, so it looks safe to merge.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title names the Bun runtime module-reload fix, which matches the single change in moduleUtils.ts (jiti configured with tryNative: false so Bun uses jiti's loader instead of native import()). The t…
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.
Description Check
Check skipped - CodeRabbit’s high-level summary is enabled.
Full details: Title check
Explanation
The title names the Bun runtime module-reload fix, which matches the single change in moduleUtils.ts (jiti configured with tryNative: false so Bun uses jiti's loader instead of native import()). The title is specific and on topic. It uses the conventional commit prefix 'fix(utils):', which fits the change. It does not name jiti or the cache behavior, but it does not need to.
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: 8a4a9d0c-e863-4014-a87a-66dac5880eae
Commits
Reviewing files that changed from the base of the PR and between 49566e1 and a3c1250.
Files selected for processing: 1
packages/docusaurus-utils/src/moduleUtils.ts
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
With
docusaurus starton the Bun runtime, editingdocusaurus.config.tsreloads the config, but not the modules it imports: they keep their old values until the dev server restarts. The same goes for sidebars and plugins loaded withloadFreshModule().jiti defaults to
tryNative: "Bun" in globalThis: on Bun, it loads modules with the nativeimport(), whose module cache lives as long as the process. OurmoduleCache: falseoption doesn't bypass it. WithtryNative: false, jiti uses its own loader on Bun too, like on Node.js.The bunosaurus fork found and fixed the same problem.
Test Plan
Vitest runs on Node.js, so I tested it manually on a new classic site whose
docusaurus.config.tsimportstaglinefrom asiteTagline.tsmodule. I randocusaurus start, changedsiteTagline.ts, then edited the config to trigger a reload, and checked.docusaurus/docusaurus.config.mjs:--bun)Test links
Deploy preview: https://deploy-preview-13026--docusaurus-2.netlify.app/
Related issues/PRs
Running on Bun with
--bunalso needs #13024🤖 Generated with Claude Code