Skip to content

[Snyk] Fix for 1 vulnerabilities#752

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

[Snyk] Fix for 1 vulnerabilities#752
chrislin22 wants to merge 1 commit into
2.10_dsfrom
snyk-fix-ab971e6818d849444cb83ae38b4e9da8

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 Inefficient Algorithmic Complexity
SNYK-JS-BRACEEXPANSION-17706650
  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 large upgrade with multiple high-impact major version changes. The most significant is the Docusaurus v2 to v3 migration, which requires environment and content changes. The npm and replace-in-file upgrades also introduce notable breaking changes.

@docusaurus/core, @docusaurus/preset-classic, @docusaurus/plugin-client-redirects (v2 → v3)

This is a major migration with several required actions. The primary breaking change is the upgrade from MDX v1 to MDX v3, which enforces stricter parsing of Markdown files.

Breaking Changes:

  • Node.js Requirement: Docusaurus v3 requires Node.js v18.0 or newer.
  • React v18: Requires React v18, which may introduce subtle breaking changes in custom components, particularly around automatic batching and new hydration errors.
  • MDX v3: Content files with JSX, unescaped < or { characters may fail to build. The npx docusaurus-mdx-checker tool can be used to identify problematic files.
  • Admonitions: The :::caution admonition is deprecated in favor of :::warning.

Recommendation:

  1. Ensure your deployment environment and local development use Node.js v18+.
  2. Run npx docusaurus-mdx-checker to find and fix content files that are not compliant with MDX v3.
  3. Review custom React components for compatibility with React 18.
  4. Replace :::caution with :::warning in your markdown files.

Source: Docusaurus v3 Upgrade Guide, Docusaurus 3.0 Release Notes

npm (8.19.4 → 11.6.4)

This upgrade spans three major versions (v9, v10, v11) and introduces several breaking changes, primarily related to environment support and command behavior.

Breaking Changes:

  • Node.js Support:
    • npm v9: Dropped support for Node.js <14.17. It requires ^14.17.0 || ^16.13.0 || &gt;=18.0.0.
    • npm v10: Dropped support for Node 14 and 16. It requires ^18.17.0 || &gt;=20.5.0.
    • npm v11: Requires Node.js ^20.17.0 || &gt;=22.9.0.
  • npm v9: npm pack now has stricter ignore rule processing. The adduser command has changed, and npm login is now preferred for authentication.
  • npm v10: No longer automatically retries on 409 Conflict during publish. The ci-name config has been removed.
  • npm v11: The npm hook command has been removed. Publishing pre-release versions now requires an explicit --tag.

Source: npm v9, v10, v11 Changelogs

replace-in-file (6.3.5 → 8.3.1)

This upgrade to v8 is a significant breaking change, converting the package to an ES Module (ESM).

Breaking Changes:

  • Node.js Requirement: Version 8.0.0 requires Node.js 18 or higher.
  • ESM Only: The package is now an ES Module. You must use import { replaceInFile } from 'replace-in-file' instead of require(). Default exports are no longer provided.
  • API Changes: The callback-based API has been removed in favor of Promises (async/await). The replace.sync method is now a named export replaceInFileSync.

Source: replace-in-file Changelog

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