fix: update vue-renderer-markdown dependency to version 0.0.63-beta.0…

[Simon-He95]

… and adjust CSS import

Summary by CodeRabbit

• Chores

  • Updated development dependencies to latest versions.

• Style

  • Refined styling configuration imports for better maintainability.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The PR updates the vue-renderer-markdown dependency from version 0.0.62-beta.1 to 0.0.63-beta.0 and changes the imported CSS file from index.css to index.tailwind.css in the renderer styles.

Changes

Cohort / File(s)	Summary
Dependency Update package.json	Updated vue-renderer-markdown devDependency from 0.0.62-beta.1 to 0.0.63-beta.0
CSS Import Path src/renderer/src/assets/style.css	Changed vue-renderer-markdown CSS import from index.css to index.tailwind.css in @layer base

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat: upgrade vue-renderer-markdown support code_block collpase and mermaid progressive render #903: Both PRs change the vue-renderer-markdown CSS import from index.css to index.tailwind.css and update the same dependency.
• chore: update vue-renderer-markdown & vue-use-monaco deps to perf use Monaco use raf render #896: Both PRs update the vue-renderer-markdown dependency version.
• fix: table style #943: Both PRs modify the vue-renderer-markdown dependency and involve Tailwind-related stylesheet changes.

Suggested reviewers

• zerob13

Poem

🐰 A hop and a bump of the version so fine,
CSS streams rerouted through tailwind's design,
Dependencies updated with care and with might,
The renderer now styled just perfectly right! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main changes: updating the vue-renderer-markdown dependency to version 0.0.63-beta.0 and adjusting the CSS import, matching the actual changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1d526df and ba6385f.

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/renderer/src/assets/style.css (1 hunks)

🧰 Additional context used

🧠 Learnings (3)

📓 Common learnings

Learnt from: neoragex2002
Repo: ThinkInAIXYZ/deepchat PR: 807
File: src/renderer/src/components/markdown/MarkdownRenderer.vue:58-58
Timestamp: 2025-08-28T08:07:05.182Z
Learning: In src/renderer/src/components/markdown/MarkdownRenderer.vue, the unscoped <style> tag is intentionally used for global prose styles and the anchor .markdown-renderer fix, as confirmed by user neoragex2002.

📚 Learning: 2025-08-28T08:07:05.182Z

Learnt from: neoragex2002
Repo: ThinkInAIXYZ/deepchat PR: 807
File: src/renderer/src/components/markdown/MarkdownRenderer.vue:58-58
Timestamp: 2025-08-28T08:07:05.182Z
Learning: In src/renderer/src/components/markdown/MarkdownRenderer.vue, the unscoped <style> tag is intentionally used for global prose styles and the anchor .markdown-renderer fix, as confirmed by user neoragex2002.

Applied to files:

• src/renderer/src/assets/style.css

📚 Learning: 2025-10-12T00:58:06.513Z

Learnt from: zerob13
Repo: ThinkInAIXYZ/deepchat PR: 977
File: package.json:137-137
Timestamp: 2025-10-12T00:58:06.513Z
Learning: In this Electron project, renderer process dependencies (used only in src/renderer/) should be placed in devDependencies because they are bundled by electron-vite during the build process. Only main process dependencies (used in src/main/) need to be in the dependencies section.

Applied to files:

• package.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build-check (x64)

🔇 Additional comments (2)

package.json (2)

100-176: Correct devDependencies placement for renderer process dependency.

The vue-renderer-markdown package is correctly placed in devDependencies since it's used exclusively in the renderer process and will be bundled by electron-vite during the build.

---

169-169: The version 0.0.63-beta.0 does not exist on npm; update to 0.0.62-beta.2.

The latest published version of vue-renderer-markdown is 0.0.62-beta.2, but this PR specifies 0.0.63-beta.0. Using a non-existent version will cause npm install to fail. Either update to 0.0.62-beta.2 or confirm this is an intentional future version that will be published separately.

⛔ Skipped due to learnings

Learnt from: zerob13
Repo: ThinkInAIXYZ/deepchat PR: 977
File: package.json:137-137
Timestamp: 2025-10-12T00:58:06.513Z
Learning: In this Electron project, renderer process dependencies (used only in src/renderer/) should be placed in devDependencies because they are bundled by electron-vite during the build process. Only main process dependencies (used in src/main/) need to be in the dependencies section.

Learnt from: neoragex2002
Repo: ThinkInAIXYZ/deepchat PR: 807
File: src/renderer/src/components/markdown/MarkdownRenderer.vue:58-58
Timestamp: 2025-08-28T08:07:05.182Z
Learning: In src/renderer/src/components/markdown/MarkdownRenderer.vue, the unscoped <style> tag is intentionally used for global prose styles and the anchor .markdown-renderer fix, as confirmed by user neoragex2002.