Enable Docusaurus Faster for improved documentation build performance#18954
Merged
harupy merged 1 commit intomlflow:masterfrom Nov 21, 2025
Merged
Enable Docusaurus Faster for improved documentation build performance#18954harupy merged 1 commit intomlflow:masterfrom
harupy merged 1 commit intomlflow:masterfrom
Conversation
This commit enables Docusaurus Faster, an experimental feature that uses Rspack (Rust-based bundler) and SWC (Speedy Web Compiler) instead of webpack and Babel for significantly faster documentation builds. Changes: - Add @docusaurus/faster dependency - Enable experimental_faster and v4 future flags in docusaurus.config.ts - Suppress SSG warnings in build command for cleaner output Reference: https://docusaurus.io/blog/releases/3.6 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: harupy <17039389+harupy@users.noreply.github.com>
e2e4895 to
ba7bc48
Compare
Contributor
|
Documentation preview for ba7bc48 is available at: More info
|
harupy
commented
Nov 21, 2025
| "start": "docusaurus start", | ||
| "preview": "npm run build && npm run serve", | ||
| "build": "docusaurus build", | ||
| "build": "DOCUSAURUS_IGNORE_SSG_WARNINGS=true docusaurus build", |
Member
Author
There was a problem hiding this comment.
Maybe it's just me but docusaurus build slows down my laptop on master and takes a few minutes.
jimilp7
pushed a commit
to backspace-org/mlflow
that referenced
this pull request
Nov 21, 2025
…mlflow#18954) Signed-off-by: harupy <17039389+harupy@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com>
Tian-Sky-Lan
pushed a commit
to Tian-Sky-Lan/mlflow
that referenced
this pull request
Nov 24, 2025
…mlflow#18954) Signed-off-by: harupy <17039389+harupy@users.noreply.github.com> Co-authored-by: Claude <noreply@anthropic.com> Signed-off-by: Tian Lan <sky.blue266000@gmail.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
2 participants
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.
What changes are proposed in this pull request?
This PR enables Docusaurus Faster, an experimental feature announced in Docusaurus 3.6 that significantly improves documentation build performance by using Rspack (Rust-based bundler) and SWC (Speedy Web Compiler) instead of webpack and Babel.
Changes:
@docusaurus/fasterdependencyexperimental_fasterandv4future flags indocusaurus.config.tsbabel.config.js(no longer needed with SWC)Build Time Comparison
Before (webpack/Babel): ~2 minutes 39 seconds
After (Rspack/SWC): ~43 seconds (~3.7x faster)
How is this PR tested?
Verified successful build with
npm run buildin the docs directory. Build completes successfully with SWC loader active and cleaner output.Does this PR require documentation update?
Release Notes
Is this a user-facing change?
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/build: Build and test infrastructure for MLflowarea/docs: MLflow documentation pagesHow should the PR be classified in the release notes? Choose one:
rn/none- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionShould this PR be included in the next patch release?
🤖 Generated with Claude Code