fix(installation): update Vue import path and add TinyVue component example

[zzcr]

更新 Vue 导入路径并添加 TinyVue 组件示例

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features
  • The user interface now displays additional interactive elements directly on the page.
• Refactor
  • Streamlined the application setup by shifting component placement from dynamic code to the static HTML structure and updating core framework initialization.

[coderabbitai]

Walkthrough

The changes update the Vue import path and modify the HTML structure in the installation document. The Vue library is now imported from vue.esm-browser.js instead of vue.runtime.esm-browser.js. Additionally, the Vue app initialization has been simplified by removing the inline template from the JavaScript code and directly embedding the <tiny-button> and <tiny-alert> components into the HTML structure.

Changes

File	Change Summary
examples/.../installation.md	Updated Vue import path from vue.runtime.esm-browser.js to vue.esm-browser.js; removed inline JavaScript template by directly adding <tiny-button> and <tiny-alert> to the HTML

Sequence Diagram(s)

sequenceDiagram
    participant Browser as Browser
    participant HTML as HTML Document
    participant Vue as Vue Engine
    participant App as Application Container "#app"

    Browser->>HTML: Request installation page
    HTML->>Vue: Import Vue from "vue.esm-browser.js"
    Vue->>App: Initialize app (createApp() without template)
    App->>HTML: Render <tiny-button> and <tiny-alert> components

Loading

Poem

I’m a rabbit with a coder’s cheer,
Hopping through changes, fresh and clear.
Vue imports now shine a brighter light,
With buttons tiny and alerts just right.
Code and carrots, what a delight!
🐇✨
Let’s hop into this new digital fight!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 358d642 and 1689bb7.

📒 Files selected for processing (1)

• examples/sites/demos/pc/webdoc/installation.md (2 hunks)

🔇 Additional comments (3)

examples/sites/demos/pc/webdoc/installation.md (3)

95-95: Vue Import Path Update
The intent is to update the Vue import so that the full build (with the template compiler) is used. However, the current line still references "vue.runtime.esm-browser.js" instead of the expected "vue.esm-browser.js". Please verify that this is intentional and update the URL if the goal is to use the full build for template compilation.

---

115-117: Embedding TinyVue Components in HTML
The new inclusion of <tiny-button> and <tiny-alert> within the #app div provides a clear example of TinyVue component usage. Make sure that these components are registered globally (via the TinyVue plugin) and that any associated styles or documentation are updated accordingly.

---

124-124: Simplified App Initialization Consideration
By calling createApp() without a root component and relying on the inner HTML as the template, the initialization is simplified. However, note that Vue’s API typically expects a root component (even an empty object, as in createApp({})) to ensure predictable template compilation. Please verify that this call works as intended across your target environments and consider explicitly passing an empty component to avoid ambiguity.
[request_verification, suggest_good_to_have_refactor]

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

[e2e-test-warn]
The component to be tested is missing.

The title of the Pull request should look like "fix(vue-renderless): [action-menu, alert] fix xxx bug".

Please make sure you've read our contributing guide