feat(docs): add enterprise vector icons, Mermaid zoom modal, and security overrides

[Kuldeep2822k]

Applies enterprise styling enhancements, security audit overrides, and Mermaid interactive diagram zoom/pan modal.

[greptile-apps]

Kuldeep2822k has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

[coderabbitai]

Warning

Review limit reached

@Kuldeep2822k, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Free

Run ID: 4d35194b-2e17-4c07-be0b-4f0237bff7a4

📥 Commits

Reviewing files that changed from the base of the PR and between 7c590ea and 7eb1960.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (4)

• docs/.vitepress/config.mts
• docs/.vitepress/theme/MermaidZoom.vue
• docs/.vitepress/theme/custom.css
• package.json

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Free

Run ID: 8487e3d9-9d29-4dd1-9314-68d8797a6d52

📥 Commits

Reviewing files that changed from the base of the PR and between 37ce510 and 7c590ea.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (5)

• docs/.vitepress/theme/MermaidZoom.vue
• docs/.vitepress/theme/custom.css
• docs/.vitepress/theme/index.ts
• docs/index.md
• package.json

---

📝 Walkthrough

Summary by CodeRabbit

• New Features

  • Added interactive Mermaid diagrams with click-to-zoom, pan, reset, and full-screen modal viewing.
  • Diagrams added dynamically to documentation pages are supported automatically.
  • Added keyboard and modal controls, including Escape-to-close.

• Style

  • Introduced an enterprise-inspired dark theme with blue branding.
  • Improved Mermaid diagram hover states and zoom affordances.
  • Refreshed feature cards with modern backgrounds, borders, icons, and hover effects.

Walkthrough

The VitePress documentation theme adds interactive Mermaid diagram zooming and panning. It also adds dark-theme styling, SVG feature icons, theme integration, and Vite and esbuild version overrides.

Changes

Documentation theme

Layer / File(s)	Summary
Mermaid diagram zoom flow docs/.vitepress/theme/MermaidZoom.vue	The new component discovers Mermaid diagrams, opens SVGs in a modal, supports zooming, panning, reset, Escape-to-close, scroll locking, and dynamic diagram detection.
Theme wiring and visual presentation docs/.vitepress/theme/index.ts, docs/.vitepress/theme/custom.css, docs/index.md	The custom theme loads the component and stylesheet. Dark-theme styles, Mermaid interaction styles, feature-card styles, and inline SVG icons are added.
Build dependency overrides package.json	Overrides pin vite to ^6.4.3 and esbuild to ^0.25.0.

Estimated code review effort: 4 (Complex) | ~45 minutes

Merge Risk: ⚪ Minimal · up to 7c590

This documentation-focused change has no actionable merge-blocking risk identified at the current head and is merge-ready after normal checks and review.

Sequence Diagram(s)

sequenceDiagram
  participant MermaidContainer
  participant MermaidZoom
  participant ZoomModal
  participant SVGViewport
  MermaidContainer->>MermaidZoom: Click diagram
  MermaidZoom->>ZoomModal: Open SVG modal
  ZoomModal->>SVGViewport: Render transformed SVG
  SVGViewport->>MermaidZoom: Send wheel or drag input
  MermaidZoom->>SVGViewport: Update zoom or pan
  MermaidZoom->>ZoomModal: Close on overlay or Escape

Loading

Poem

A rabbit clicks the diagram with care,
Zooms through SVGs floating in air.
Blue cards glow and dark panels gleam,
Pans move smoothly across the stream.
Dependencies stay neatly pinned,
Documentation hops with a grin.

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login.

_{Comment @coderabbitai help to get the list of available commands.}

[qodo-code-review]

PR Summary by Qodo

Add enterprise docs theme, Mermaid zoom/pan modal, and dependency overrides

✨ Enhancement 📝 Documentation ⚙️ Configuration changes 🕐 20-40 Minutes

AI Description

• Add click-to-zoom/pan modal for Mermaid diagrams in VitePress docs.
• Apply enterprise dark theme styling and replace emoji feature icons with SVG.
• Pin Vite/esbuild via overrides and refresh lockfile for security/tooling alignment.

Diagram

graph TD
  A["VitePress Layout"] --> B["theme/index.ts"] --> C["MermaidZoom.vue"] --> D["Mermaid DOM (svg)"] --> E["Zoom Modal Overlay"]
  A --> F["custom.css"]
  G["docs/index.md"] --> A
  H["package.json overrides"] --> I["package-lock.json"]

  subgraph Legend
    direction LR
    _doc["Doc content"] ~~~ _cfg["Build config"] ~~~ _ui["UI component"]
  end

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Use svg-pan-zoom (or similar) instead of custom transforms

• ➕ Battle-tested pan/zoom behavior (including touch/pinch, boundaries, inertia)
• ➕ Less bespoke event logic and edge-case handling
• ➖ Adds a client dependency and bundle weight to docs
• ➖ Still requires wiring to Mermaid-rendered SVG lifecycle

2. Implement zoom as a VitePress/Vue directive instead of a layout component + MutationObserver

• ➕ More targeted attachment (per Mermaid container) and easier teardown
• ➕ Less global DOM observation overhead
• ➖ Requires ensuring directive runs after Mermaid rendering and on route changes
• ➖ May still need a watcher for dynamically rendered diagrams

3. Prefer pure-CSS/HTML zoom (open SVG in new tab or dialog without pan logic)

• ➕ Very low complexity and minimal JS
• ➕ Avoids global listeners and drag state
• ➖ No pan/zoom controls; poor usability for large diagrams
• ➖ Less consistent experience across browsers

Recommendation: The current approach is reasonable for a docs site: it avoids adding a third-party pan/zoom dependency and provides a consistent modal UX. If performance becomes a concern, consider replacing the MutationObserver-based attachment with a directive or route-change hook so listeners are attached only when Mermaid content is known to be present.

Files changed (6) +4064 / -3622

Enhancement (1) +250 / -0

MermaidZoom.vueAdd Mermaid SVG zoom/pan modal component +250/-0

Add Mermaid SVG zoom/pan modal component

• Introduces a client-side modal that captures Mermaid-rendered SVG HTML on click and renders it full-screen. Adds zoom controls (wheel/buttons), drag-to-pan, Escape-to-close, and a MutationObserver to attach listeners to newly rendered Mermaid blocks.

docs/.vitepress/theme/MermaidZoom.vue

Documentation (1) +17 / -6

index.mdReplace homepage feature emojis with inline SVG icons +17/-6

Replace homepage feature emojis with inline SVG icons

• Updates the hero feature list to use inline SVG icon definitions instead of emoji characters, matching the new enterprise icon container styling.

docs/index.md

Other (4) +3797 / -3616

custom.cssAdd enterprise dark theme styling and Mermaid/feature card polish +95/-0

Add enterprise dark theme styling and Mermaid/feature card polish

• Defines brand colors and dark theme background variables. Styles Mermaid containers as interactive (hover affordance and hint) and modernizes feature cards and icon containers for an enterprise look.

docs/.vitepress/theme/custom.css

index.tsWire custom theme assets and mount MermaidZoom in layout +13/-0

Wire custom theme assets and mount MermaidZoom in layout

• Extends VitePress DefaultTheme, imports the custom CSS, and injects MermaidZoom via the layout slot so it is available site-wide.

docs/.vitepress/theme/index.ts

package-lock.jsonUpdate lockfile for Vite 6 / esbuild changes and nested esbuild entries +3685/-3616

Update lockfile for Vite 6 / esbuild changes and nested esbuild entries

• Reflects dependency graph changes after upgrading/pinning Vite and esbuild, including removal of prior top-level esbuild entries and addition of nested esbuild packages (e.g., under tsx/vite).

package-lock.json

package.jsonAdd overrides to pin Vite and esbuild versions +4/-0

Add overrides to pin Vite and esbuild versions

• Adds npm overrides to force specific Vite and esbuild ranges, aligning the docs toolchain with required versions (e.g., security audit overrides).

package.json

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Light cards lose contrast ✓ Resolved 🐞 Bug ≡ Correctness

Description

The feature cards receive a near-black background in every color mode while their title and details
retain VitePress's active theme text colors. In light mode, all six home-page cards therefore render
low-contrast dark text on #0e1117.

Code

docs/.vitepress/theme/custom.css[R65-68]

+.VPFeature {
+  border: 1px solid #1e2430 !important;
+  background-color: #0e1117 !important;
+  border-radius: 12px !important;

Relevance

●●● Strong

Obvious light-mode contrast regression in docs styling; teams usually accept straightforward CSS
scoping fixes.

PR-#61
PR-#60

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The custom theme scopes its dark palette to .dark but applies #0e1117 to .VPFeature globally.
VitePress's feature component uses theme-driven text coloring, including var(--vp-c-text-2) for
details, and the home page defines six affected cards.

docs/.vitepress/theme/custom.css[9-16]
docs/.vitepress/theme/custom.css[64-75]
docs/index.md[19-48]
🌐 VitePress's feature component uses the active theme's text colors, including var(--vp-c-text-2) for detail text.

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The unconditional dark feature-card background conflicts with VitePress light-mode text colors.

## Issue Context
Scope the dark background and border to `.dark`, and provide light-mode card colors through VitePress variables or matching text colors.

## Fix Focus Areas
- docs/.vitepress/theme/custom.css[64-75]
- docs/index.md[19-48]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Unsanitized SVG rendered via v-html ✓ Resolved 🐞 Bug ⛨ Security

Description

MermaidZoom.vue captures the rendered Mermaid SVG's outerHTML and re-inserts it into the DOM via
v-html without any sanitization (e.g. DOMPurify), creating an unsafe HTML injection boundary. If any
diagram source can influence the SVG markup Mermaid emits, this becomes an XSS vector since Vue does
not sanitize v-html content.

Code

docs/.vitepress/theme/MermaidZoom.vue[R88-93]

+      el.addEventListener('click', (e) => {
+        const svg = el.querySelector('svg')
+        if (svg) {
+          openModal(svg.outerHTML)
+        }
+      })

Relevance

●●● Strong

Team has accepted security hardening changes; unsanitized v-html is a clear XSS boundary worth
fixing.

PR-#12

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The click handler grabs svg.outerHTML and passes it to openModal (line 91), which stores it in
activeSvg (a ref) at line 14, and this is later injected via v-html="activeSvg" at template line
158. Vue's documentation states v-html content is inserted as raw HTML with no automatic
sanitization, so any executable attributes/elements present in the serialized SVG would run in the
visitor's browser.

docs/.vitepress/theme/MermaidZoom.vue[88-93]
docs/.vitepress/theme/MermaidZoom.vue[158-158]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
MermaidZoom.vue reads the outerHTML of a rendered Mermaid SVG and injects it into the DOM via Vue's `v-html`, without any sanitization step. `v-html` performs no automatic sanitization, so if the serialized SVG markup ever contains executable content (e.g. `<script>`, `on*` event handler attributes, or `javascript:` URLs within `xlink:href`/`href`), it will execute in the visitor's browser.

## Issue Context
- `openModal` receives raw `svg.outerHTML` from the DOM and stores it in the `activeSvg` ref.
- The modal template renders `activeSvg` with `v-html`.
- Mermaid diagram sources currently come from static markdown authored in-repo, but the pattern is unsafe as a general practice and would become exploitable if diagram content ever originates from less trusted sources.

## Fix Focus Areas
- docs/.vitepress/theme/MermaidZoom.vue[88-93]
- docs/.vitepress/theme/MermaidZoom.vue[158-158]
- Add a sanitization step (e.g. DOMPurify configured to allow SVG tags/attributes) before assigning `activeSvg`, or avoid re-serializing/re-parsing the SVG altogether by cloning the DOM node instead of using `v-html`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

3. Backdrop cannot close modal ✓ Resolved 🐞 Bug ≡ Correctness

Description

The overlay's click.self handler never receives apparent backdrop clicks because the full-screen
viewport child is the event target. Users can dismiss the modal only with Escape or the close
button.

Code

docs/.vitepress/theme/MermaidZoom.vue[127]

+  <div v-if="isOpen" class="mermaid-modal-overlay" @click.self="closeModal">

Relevance

●●● Strong

Small, user-visible modal usability bug; likely to be fixed when pointed out.

PR-#61

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The self-only handler is on the overlay, while its viewport child is explicitly sized to the entire
screen; therefore clicks in the visible backdrop target the viewport rather than the overlay.

docs/.vitepress/theme/MermaidZoom.vue[127-151]
docs/.vitepress/theme/MermaidZoom.vue[226-233]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The full-screen viewport intercepts backdrop clicks, so the overlay's `@click.self` handler cannot close the modal.

## Issue Context
Keep clicks on the diagram and toolbar from closing the modal while allowing clicks on empty viewport space to dismiss it.

## Fix Focus Areas
- docs/.vitepress/theme/MermaidZoom.vue[127-151]
- docs/.vitepress/theme/MermaidZoom.vue[226-233]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

4. Unfiltered MutationObserver triggers full-page rescans ✓ Resolved 🐞 Bug ➹ Performance

Description

The MutationObserver in MermaidZoom.vue observes the entire document.body subtree for any
childList change and, on every single mutation anywhere on the page, calls
attachMermaidListeners(), which runs document.querySelectorAll across the whole document inside
a queued nextTick. This causes repeated, unfiltered full-document DOM queries on unrelated page
mutations (e.g. VitePress navigation, search widget updates, sidebar toggles), which is wasteful and
can accumulate as more nextTick callbacks are queued than necessary.

Code

docs/.vitepress/theme/MermaidZoom.vue[R105-112]

+    observer = new MutationObserver(() => {
+      attachMermaidListeners()
+    })
+
+    observer.observe(document.body, {
+      childList: true,
+      subtree: true
+    })

Relevance

●● Moderate

Performance concern is plausible but debouncing/filtering is subjective without matching prior
review precedent.

PR-#61

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The observer callback (lines 105-107) takes no mutation records into account and always calls
attachMermaidListeners(), which schedules a nextTick that runs querySelectorAll('.mermaid,
[data-mermaid], .vp-mermaid') over the full document (line 80) on every observed body mutation
(childList+subtree, lines 109-112), with no debouncing or filtering of mutation targets.

docs/.vitepress/theme/MermaidZoom.vue[77-96]
docs/.vitepress/theme/MermaidZoom.vue[105-112]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The MutationObserver observing `document.body` with `subtree: true` invokes a full-document `querySelectorAll` scan on every single DOM mutation anywhere on the page, without inspecting the mutation records or debouncing calls.

## Issue Context
- The observer is set up in `onMounted` and never filtered.
- `attachMermaidListeners` is scheduled via `nextTick` on every mutation callback invocation, and can be queued many times in quick succession for unrelated DOM changes (navigation, VitePress UI updates, etc.).

## Fix Focus Areas
- docs/.vitepress/theme/MermaidZoom.vue[77-96]
- docs/.vitepress/theme/MermaidZoom.vue[98-113]
- Debounce the observer callback and/or inspect `mutations[].addedNodes` to only rescan when relevant nodes are added, and scope observation to the main content container instead of `document.body`.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

5. Touch users cannot pan ✓ Resolved 🐞 Bug ≡ Correctness

Description

The modal binds only wheel and mouse events, leaving touch-only users without reliable drag-to-pan
support. After toolbar zoom moves content off-screen, mobile and tablet users cannot navigate to it.

Code

docs/.vitepress/theme/MermaidZoom.vue[R146-149]

+      @wheel="handleWheel"
+      @mousedown="handleMouseDown"
+      @mousemove="handleMouseMove"
+      @mouseup="handleMouseUp"

Relevance

●● Moderate

Adding touch/pointer support is a feature expansion; may be deferred unless required for docs UX.

PR-#61

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

All drag state is driven by MouseEvent, and the template exposes only wheel/mouse bindings; the
component contains no pointer or touch event path.

docs/.vitepress/theme/MermaidZoom.vue[46-69]
docs/.vitepress/theme/MermaidZoom.vue[144-151]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The zoom modal supports mouse dragging but not reliable touch panning.

## Issue Context
Implement Pointer Events for mouse, pen, and touch, use pointer capture during dragging, and set an appropriate `touch-action` on the viewport.

## Fix Focus Areas
- docs/.vitepress/theme/MermaidZoom.vue[55-69]
- docs/.vitepress/theme/MermaidZoom.vue[144-151]
- docs/.vitepress/theme/MermaidZoom.vue[226-233]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

6. npm override forces Vite major version bump 🐞 Bug ☼ Reliability

Description

package.json forces tree-wide npm overrides to vite ^6.4.3 and esbuild ^0.25.x even though
VitePress 1.6.4 declares vite ^5.4.14 and tsx 4.23.11 declares esbuild ~0.28.0, pushing both
consumers outside their stated compatibility ranges. This is a legitimate but unverified
compatibility risk for the docs build/dev pipeline and tsx-driven workflows, and it shouldn’t be
treated as a safe remediation without upgrading the consumers or explicitly validating the resulting
combinations.

Code

package.json[R54-56]

+  "overrides": {
+    "vite": "^6.4.3",
+    "esbuild": "^0.25.0"

Relevance

●● Moderate

Overrides align with PR intent (“security overrides”) but forcing major/toolchain versions is risky;
outcome uncertain.

PR-#12

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The lockfile evidence shows VitePress 1.6.4 requesting vite: ^5.4.14 while the dependency graph
resolves Vite 6.4.3 due to the global override, demonstrating the override bypasses VitePress’s
declared range. It also records tsx 4.23.11 requesting esbuild: ~0.28.0 while a nested esbuild
resolves to 0.25.12 under the override, proving tsx is likewise being forced outside its stated
range. The referenced upstream VitePress information indicates this release line was still on Vite 5
and that official Vite 6 support was introduced via a dedicated breaking-change PR (and that mixing
Vite 5/6 types can be incompatible), reinforcing that VitePress 1.6.4’s declared range was not
written with Vite 6 in mind and that overriding it is an unverified compatibility bet.

package-lock.json[6172-6172]
package.json[54-56]
package-lock.json[4887-4900]
package-lock.json[5348-5362]
package-lock.json[5590-5608]
package-lock.json[6149-6173]
🌐 PR titled 'feat!: upgrade vite to v6' description notes it's a breaking change in Vite requiring a major/minor VitePress version bump to adopt it properly.
🌐 The VitePress issue requests Vite 6 support because VitePress was still using Vite 5 and shows cross-version plugin type incompatibilities.

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`package.json` introduces global npm `overrides` forcing `vite` to `^6.4.3` and `esbuild` to `^0.25.x`, but VitePress 1.6.4 declares `vite: ^5.4.14` and tsx 4.23.11 declares `esbuild: ~0.28.0`. These overrides bypass the consumers’ declared compatibility ranges and can break the docs build/dev pipeline and/or tsx workflows unless the combinations are explicitly validated or the consumers are upgraded.

## Issue Context
- The overrides appear intended as remediation (e.g., addressing an esbuild advisory), but have the side effect of forcing a Vite major-version jump for VitePress.
- `package-lock.json` records VitePress 1.6.4 requesting Vite `^5.4.14` while resolving Vite 6.4.3, and tsx 4.23.11 requesting esbuild `~0.28.0` while resolving esbuild 0.25.12.
- Upstream VitePress documentation/PR history indicates Vite 6 support was added via a dedicated breaking-change PR (e.g., vuejs/vitepress#4467/#4504), suggesting VitePress 1.6.4 was not necessarily validated against Vite 6; mixing Vite 5/6 types is noted as a potential incompatibility.

## Fix Focus Areas
- package.json[54-56]
- package-lock.json[4887-4895]
- package-lock.json[5590-5608]
- package-lock.json[6149-6173]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context

✅ Web pages:

  🌐 Upgrade VitePress to use Vite `v6`

  🌐 feat!: upgrade vite to v6 · Pull Request #4467 · vuejs/vitepress

  🌐 Fix vite/esbuild security advisories (REV-37, Dependabot #14–#17)

  +29 more

Review mode: 🧠 Deep: This PR combines a new interactive Vue component, global theme/config changes, and dependency overrides with many independent behavioral and compatibility risks that benefit from redundant review passes.

Tip of the day

💡 Did you know, you can turn on the rule miner and Qodo learns your standards from review history

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

6. Npm override forces vite major version bump 🐞 Bug ☼ Reliability

package.json forces tree-wide npm overrides to vite ^6.4.3 and esbuild ^0.25.x even though
VitePress 1.6.4 declares vite ^5.4.14 and tsx 4.23.11 declares esbuild ~0.28.0, pushing both
consumers outside their stated compatibility ranges. This is a legitimate but unverified
compatibility risk for the docs build/dev pipeline and tsx-driven workflows, and it shouldn’t be
treated as a safe remediation without upgrading the consumers or explicitly validating the resulting
combinations.

Agent Prompt

## Issue description
`package.json` introduces global npm `overrides` forcing `vite` to `^6.4.3` and `esbuild` to `^0.25.x`, but VitePress 1.6.4 declares `vite: ^5.4.14` and tsx 4.23.11 declares `esbuild: ~0.28.0`. These overrides bypass the consumers’ declared compatibility ranges and can break the docs build/dev pipeline and/or tsx workflows unless the combinations are explicitly validated or the consumers are upgraded.

## Issue Context
- The overrides appear intended as remediation (e.g., addressing an esbuild advisory), but have the side effect of forcing a Vite major-version jump for VitePress.
- `package-lock.json` records VitePress 1.6.4 requesting Vite `^5.4.14` while resolving Vite 6.4.3, and tsx 4.23.11 requesting esbuild `~0.28.0` while resolving esbuild 0.25.12.
- Upstream VitePress documentation/PR history indicates Vite 6 support was added via a dedicated breaking-change PR (e.g., vuejs/vitepress#4467/#4504), suggesting VitePress 1.6.4 was not necessarily validated against Vite 6; mixing Vite 5/6 types is noted as a potential incompatibility.

## Fix Focus Areas
- package.json[54-56]
- package-lock.json[4887-4895]
- package-lock.json[5590-5608]
- package-lock.json[6149-6173]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[greptile-apps]

Kuldeep2822k has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

[greptile-apps]

Kuldeep2822k has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

[greptile-apps]

Kuldeep2822k has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

[greptile-apps]

Kuldeep2822k has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.