build(deps): bump md-editor-v3 from 6.5.0 to 6.5.4

[dependabot]

Bumps md-editor-v3 from 6.5.0 to 6.5.4.

Release notes

Sourced from md-editor-v3's releases.

v6.5.4

See full changelog in CHANGELOG.md.

Full Changelog: imzbf/md-editor-v3@v6.5.3...v6.5.4

v6.5.3

See full changelog in CHANGELOG.md.

Full Changelog: imzbf/md-editor-v3@v6.5.2...v6.5.3

v6.5.2

See full changelog in CHANGELOG.md.

Full Changelog: imzbf/md-editor-v3@v6.5.1...v6.5.2

v6.5.1

See full changelog in CHANGELOG.md.

Full Changelog: imzbf/md-editor-v3@v6.5.0...v6.5.1

Changelog

Sourced from md-editor-v3's changelog.

6.5.4 (2026-07-17)

Fixed Bugs

• escape code fence metadata in preview output (commit 2c07360)

• fix misalignment when syncing editor to preview at the top (commit bea48ec)

  • 描述

  • • 修复 pEleHandler 中 startTop === 0 且无显式初始块时的隐式高度计算，避免开头留白时映射错误。
  • • 修改 getLineNumber 倒序遍历逻辑
  • • 移除冗余的越界条件判断

  • 问题

  • 编辑区开头有空白时滑动，预览区会直接跳到文档中段

  • 解决

  • • 如果“文档中只存在一个模块”，实际应该被触底逻辑覆盖
  • • startEle === endEle条件在buildMap隐式填充0、且无多余DOM才会进入，对应预览区域无实际dom，直接置零
  • (cherry picked from commit 389f926b18030ef1c80c900472d44ed6957dbcb7)

• fix misalignment when syncing preview to editor at the top (commit ea6f13b)

  • Description

  • Fixed a bug where the editor and preview areas failed to align at the top when scrolling the preview area.

  • Cause

  • In cEleHandler (preview-to-editor), when realEleStart matches the first child, scale is calculated from absolute 0, but firstLineScrollTop was not reset to 0. This caused the old/cached firstLineScrollTop value to be added, preventing the editor from scrolling back to the absolute top.

  • Solution

  • Explicitly set firstLineScrollTop = 0 inside the else if branch for the top element area to ensure a proper 0-based scale mapping.
  • (cherry picked from commit d3ebcfe19dbbd7e9dd385ac143a331879f321fce)

Full Changelog: v6.5.3...v6.5.4

---

6.5.3 (2026-06-23)

Fixed Bugs

• include markdown theme as runtime dependency (commit b2b3250)
  • Move @​vavt/markdown-theme into production dependencies and align preview style imports with the generated CSS output.
  • Also update related logical style properties for search and clip controls.

Full Changelog: v6.5.2...v6.5.3

---

6.5.2 (2026-06-22)

Refactors

• replace Less with Sass and optimize project build scripts (commit cb7410d)

Fixed Bugs

... (truncated)

Commits

• 701a5f8 6.5.4
• 2c07360 fix(preview): escape code fence metadata in preview output
• bea48ec fix(scroll): fix misalignment when syncing editor to preview at the top
• ea6f13b fix(scroll): fix misalignment when syncing preview to editor at the top
• 864a432 docs(changelog): update for v6.5.3
• 716bedb 6.5.3
• b73f8ef Merge remote-tracking branch 'origin/develop'
• b2b3250 fix(preview): include markdown theme as runtime dependency
• b3f07a2 docs(changelog): update for v6.5.2
• 07626d8 6.5.2
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[github-actions]

🤖 Codex-Style Code Review by OpenCode (Vue Best Practice Enabled)

💡 Autonomous AI Reviewer inspecting git commit history and Vue code quality.

Review complete. This is a dependency-only PR: md-editor-v3 ^6.5.0 → ^6.5.4 (patch bump), with the lockfile updating its internals (lucide-vue-next → @lucide/vue@1.47.0, adding @vavt/markdown-theme@5.0.2).

Findings:

• No .ts/.vue changes; app code untouched.
• The swap is internal to md-editor-v3 — src/views/Editor.vue (sole consumer) only uses MdEditor, ToolbarNames, preview-theme="github", all stable across minor bumps.
• Lockfile is consistent (npm install --package-lock-only --dry-run → up to date); no direct imports of the swapped deps exist.

Verdict: Approve. Report written to review_report.md.
e@1.47.0and@vavt/markdown-theme@5.0.2, and removes lucide-vue-next@0.543.0`.

The merge commit ae352e4 contributes only these dependabot changes on top of the base branch; it does not drag in unrelated files.

Vue 3 / App Compatibility Check

The app's only usage of md-editor-v3 is in src/views/Editor.vue:

• import { MdEditor } from 'md-editor-v3' + md-editor-v3/lib/style.css
• import type { ToolbarNames } and preview-theme="github"

The dependency swap (lucide-vue-next → @lucide/vue) and the new @vavt/markdown-theme are internal to md-editor-v3 (bundled as its dependencies). Neither lucide-vue-next, @lucide/vue, nor @vavt/markdown-theme is imported anywhere in src/, so the transitive change is invisible to application code. The stable public API surface used (MdEditor, ToolbarNames, preview-theme) is unaffected by a patch bump within ^6.5.0, and no code changes were needed.

Upgrading to ^6.5.4 simply pins a newer patch of the already-resolvable range — ^6.5.0 would have resolved here anyway — so this is a safe, low-risk change.

Minor Observations (non-blocking)

1. Invalid cache key: the lockfile now records "name": "@lucide/vue" with version "1.47.0" (an odd lucide versioning artifact, but resolved from npmjs or the configured registry and internally consistent — no action needed).
2. Verification note: vite build / vue-tsc were not run in this review environment; a quick local build is recommended if the repo has strict CI, since md-editor-v3 is a large editor bundle. This is routine due diligence, not a blocker.
3. The merge commit carries the default merge message rather than a descriptive one — cosmetic only.

Recommendation

Approve. Dependency-only PR, consistent lockfile, verified against the single real consumer (src/views/Editor.vue), no app-code migration required.