Lockfile & CI check.

Ensure pnpm-lock.yaml is updated and CI runs typecheck/build to catch any subtle breakages in the renderer.

Also applies to: 163-163

🏁 Script executed:

#!/bin/bash
# Verify lockfile changed and basic sanity
git status -s | rg -n 'pnpm-lock.yaml' || echo "pnpm-lock.yaml not updated"
pnpm run typecheck:web && pnpm run build:unpack

Length of output: 277

These look like runtime renderer deps; consider moving them out of devDependencies.

If vue-renderer-markdown and vue-use-monaco are imported by the app at runtime (likely in src/renderer), keeping them in devDependencies risks missing-module errors in production builds where dev deps are pruned by electron-builder. Move them to dependencies or confirm your packager includes dev deps.

Apply this minimal diff:

@@ "dependencies": {
-    "zod": "^3.25.76"
+    "zod": "^3.25.76",
+    "vue-renderer-markdown": "^0.0.47",
+    "vue-use-monaco": "^0.0.17"
@@ "devDependencies": {
-    "vue-renderer-markdown": "^0.0.47",
@@
-    "vue-use-monaco": "^0.0.17",

Run to verify imports are runtime:

Also applies to: 163-163

🏁 Script executed:

#!/bin/bash
# Expect matches under src/renderer if used at runtime.
rg -n --type=ts --type=vue -C1 -g 'src/renderer/**' -e '\bvue-renderer-markdown\b|\bvue-use-monaco\b'

Length of output: 27

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Searching src/renderer for package usage..."
rg -n -C2 -g 'src/renderer/**' -e 'vue-renderer-markdown|vue-use-monaco' --hidden || true

echo "Searching src/ for import/require/dynamic import patterns..."
rg -n -C2 -g 'src/**' -e "from ['\"](vue-renderer-markdown|vue-use-monaco)['\"]" -e "require\(['\"](vue-renderer-markdown|vue-use-monaco)['\"]\)" -e "import\(['\"](vue-renderer-markdown|vue-use-monaco)['\"]\)" --hidden || true

echo "Searching package.json and lockfiles for declarations..."
rg -n -S -e 'vue-renderer-markdown|vue-use-monaco' package.json package-lock.json yarn.lock pnpm-lock.yaml pnpm-lock.json 2>/dev/null || true

echo "If no matches are found above, run a broader repo search:"
rg -n -C2 -e 'vue-renderer-markdown|vue-use-monaco' || true

echo "Done."

Length of output: 11585

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Review upstream changelogs for breaking changes (rendering/DOMPurify/syntax).

Given the “perf use raf render” note, confirm any API/option changes in vue-renderer-markdown@0.0.45–0.0.47 don’t affect your markdown pipeline (plugins, sanitizer, code block rendering).

🌐 Web query:

Changelog or release notes for vue-renderer-markdown versions 0.0.45–0.0.47; note breaking changes or required config updates.

💡 Result:

Summary for vue-renderer-markdown 0.0.45 → 0.0.47

• Primary source: package README / release info on npm and GitHub. [1][2].

What changed (high‑level)

• 0.0.45→0.0.47 are patch/minor releases focused on streaming/UX and peer‑dependency updates; the README/notes emphasize:
  • Prop name change: component now expects content (or nodes) instead of the older value/source prop in templates — use :content (JS/TS prop remains camelCase). This requires updating templates that used :value or :source. [1]
  • Peer dependency installs are now required (vue, katex, mermaid, monaco-related packages, etc.). Install the listed peers or you will see warnings / runtime failures. [1][2]
  • Monaco editor integration: additional build/vite configuration may be required if you use the Monaco integration (see vite-plugin-monaco-editor-esm/customDistPath notes). If you do not use Monaco, this peer is optional. [1]
  • Emphasis in README that the package is streaming‑first and optimized for incremental parsing; several internal parser/DOM-update improvements were made (no user config required, but behaviour with live/partial markdown may differ). [1][2]

Breaking changes / required config updates

• Update templates/usage:
  • Replace older prop names (value/source) with :content (or pass parsed nodes via :nodes). Check where you used kebab-case in templates (use :typewriter-effect for typewriterEffect, etc.). This is necessary for 0.0.45+ usage. [1]
• Install required peer dependencies listed in package.json (vue, @iconify/vue, @vueuse/core, katex, mermaid, vue-use-monaco, etc.) if your project uses the corresponding features; otherwise install only the ones you need. Failing to install required peers will trigger warnings and can break runtime features. [1]
• If you use Monaco editor features, add/adjust vite-plugin-monaco-editor-esm configuration (languageWorkers/customDistPath) as shown in the README. [1]

Where to see full, line‑by‑line release notes / changelog

• npm package page (README and publish notes): https://www.npmjs.com/package/vue-renderer-markdown. [1]
• GitHub repository (README / releases / tags / CHANGELOG in repo): https://github.com/Simon-He95/vue-markdown-render. [2]

If you want, I can fetch the exact changelog entries for 0.0.45, 0.0.46 and 0.0.47 and paste the verbatim release notes. Which would you prefer?

Sources:
[1] vue-renderer-markdown — npm package page. (npmjs.com)
[2] vue-markdown-render — GitHub repository (README / repo). (github.com)

Citations:

• 1: https://www.npmjs.com/package/vue-renderer-markdown
• 2: https://github.com/Simon-He95/vue-markdown-render