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. Action is required to ensure the site compiles and functions correctly.
Key Breaking Changes:
MDX v1 → v3 Upgrade: This is the most significant breaking change. MDX v3 is much stricter about parsing content. Markdown files (.md, .mdx) that previously worked may now fail to compile or render differently, especially those containing unescaped < or { characters. [1, 2, 3] You should use the npx docusaurus-mdx-checker command to identify files that need modification. [1, 6]
React 17 → 18 Upgrade: Docusaurus now requires React 18. [1, 2, 3] This can introduce subtle breaking changes, such as new hydration errors and differences in state update batching, which may affect custom React components or swizzled theme components. [1, 3]
Node.js Version: Support for Node.js 16 has been dropped. The new minimum required version is Node.js 18.0+. [1, 3]
Docusaurus API & Theming:
The :::caution admonition is deprecated and should be replaced with :::warning. [2]
Internal theme components have been refactored. If you have customized components using the swizzle command, you may need to re-swizzle and adapt your customizations. [2]
Recommendation:
This upgrade cannot be performed without manual intervention. Developers must follow the official migration guide carefully. Start by running the docusaurus-mdx-checker tool to estimate the content migration effort and then address the dependency and API changes.
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 3 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-AXIOS-18060730
SNYK-JS-AXIOS-18065349
SNYK-JS-AXIOS-18065355
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:
🦉 Uncontrolled Recursion
🦉 Prototype Pollution