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
This is a major upgrade from Docusaurus v2 to v3, which introduces significant and mandatory breaking changes. The upgrade requires developer action to ensure the site builds and functions correctly.
Key Breaking Changes:
MDX v1 to v3 Upgrade: This is the most significant breaking change. MDX v3 is much stricter, and content files (.md, .mdx) that worked with v2 may now fail to build. You will need to audit and update your content. A command-line tool, npx docusaurus-mdx-checker, is available to help identify files that need fixing.
Environment Requirements:
Node.js: Support for Node.js 16 is dropped. You must use Node.js 18.0+.
React: Docusaurus now requires React 18+. This may affect custom React components due to changes like automatic batching and stricter hydration checks.
Dependency Upgrades: Several core dependencies have been upgraded to new major versions, including prism-react-renderer (for code blocks) and remark-emoji.
Docusaurus API & Theming:
The :::caution admonition is deprecated and should be replaced with :::warning.
Theme components have been refactored. If you have used swizzle to customize components, you will likely need to re-swizzle and adapt your customizations.
Recommendation:
This upgrade cannot be completed without manual intervention. Follow the official Docusaurus v3 upgrade guide carefully. Plan for significant testing, especially around content rendering (MDX) and any custom React components.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
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.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
site2/website-next/package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-FASTURI-17675102
Breaking Change Risk
Important
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic
Learn how to fix vulnerabilities with free interactive lessons:
🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.