Skip to content

[Snyk] Fix for 1 vulnerabilities#751

Open
chrislin22 wants to merge 1 commit into
2.10_dsfrom
snyk-fix-0f7fffbb5833d531f484f4f7536bb026
Open

[Snyk] Fix for 1 vulnerabilities#751
chrislin22 wants to merge 1 commit into
2.10_dsfrom
snyk-fix-0f7fffbb5833d531f484f4f7536bb026

Conversation

@chrislin22

Copy link
Copy Markdown

snyk-top-banner

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.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Interpretation Conflict
SNYK-JS-FASTURI-17675102
  721  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

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.

@chrislin22

Copy link
Copy Markdown
Author

Merge Risk: High

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants