Skip to content

Remove the unused mermaid plugin and override vite to a patched release - #170

Merged
poita merged 2 commits into
mainfrom
deps/remove-mermaid-override-vite
Nov 20, 2026
Merged

poita merged 2 commits into
mainfrom
deps/remove-mermaid-override-vite

Conversation

@olaservo

Copy link
Copy Markdown
Member

Closes the ten open Dependabot alerts. Two commits.

Remove the unused mermaid plugin

Override vite to a patched 6.4.x

  • Eight vite alerts are fixed only in vite 6.4.4. The esbuild alert is fixed only in esbuild 0.25.0, which vite 6 brings in.
  • VitePress 1.6.4 is the latest stable release and depends on vite ^5.4.14. The vite 5 line ends at 5.4.21.
  • An npm overrides entry sets vite to ^6.4.4. It resolves to vite 6.4.6 and esbuild 0.25.12.
  • This puts vite outside the range VitePress declares. @vitejs/plugin-vue 5.2.4 supports vite 6.
  • Remove the override once the site moves to a VitePress release that depends on a patched vite.

Verification

  • npm run docs:build produces the same four pages as main. The built site goes from 5.0 MB to 1.5 MB.
  • npm run check:schema passes: 43 tests, 16 examples.
  • vitepress dev serves the home and specification pages.

Not addressed

npm audit also reports three moderate advisories in glob and minimatch, through typescript-json-schema 0.68.0. npm's only suggested fix is a downgrade to 0.67.1. The core specification repository pins the same version.

🤖 Generated with Claude Code

olaservo and others added 2 commits November 19, 2026 23:39
No page contains a mermaid diagram. Removing mermaid and
vitepress-plugin-mermaid drops katex and dompurify from the lockfile,
which closes the open katex advisory (GHSA-238p-pmpm-9mq7). Dependabot's
fix for it, a bump to mermaid 12, does not install because the plugin
only supports mermaid 10 and 11.

The config change is the withMermaid wrapper removed and the body
dedented.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
VitePress 1.6.4 is the latest stable release and depends on vite
^5.4.14. The vite 5 line ends at 5.4.21. Eight open advisories are
fixed only in vite 6.4.4, and the esbuild advisory only in esbuild
0.25.0, which vite 6 brings in.

The override puts vite outside the range VitePress declares.
@vitejs/plugin-vue 5.2.4 supports vite 6. Observed with vite 6.4.6:
docs:build produces the same four pages, and the dev server serves the
home and specification pages.

Remove the override once the site moves to a VitePress release that
depends on a patched vite.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@olaservo
olaservo requested a review from a team as a code owner November 20, 2026 06:46
Copilot AI balanced review requested due to automatic review settings November 20, 2026 06:46

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔵 Needs a closer look

The Vite 6 override falls outside VitePress 1.6’s declared dependency range, and production hydration, navigation, and local search still need human runtime validation.

No open issues 🎉

What changed in this PR

This PR removes unused Mermaid support from the VitePress documentation site and updates build dependencies to address the reported KaTeX, Vite, and esbuild security alerts.

Changes:

  • Remove Mermaid dependencies and the withMermaid configuration wrapper.
  • Add a temporary Vite override to ^6.4.4 while retaining VitePress 1.6.4.
  • Update the lockfile to remove Mermaid’s dependency tree and resolve Vite 6.4.6 with esbuild 0.25.12.
File Description
package.json Removes Mermaid packages and adds the patched Vite override.
package-lock.json Prunes unused dependencies, including KaTeX, and updates Vite and esbuild.
.vitepress/​config.mts Removes the Mermaid wrapper while preserving the site configuration.

Review effort: Balanced

@poita
poita merged commit 26f41b5 into main Nov 20, 2026
6 checks passed
@poita
poita deleted the deps/remove-mermaid-override-vite branch November 20, 2026 10:49
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.

3 participants