feat: add mobile dependence

[zzcr]

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

• Chores
  • Added a new development dependency @opentiny/vue-mobile to enhance project capabilities.

[coderabbitai]

Walkthrough

The changes involve the addition of a new dependency to the devDependencies section of the package.json file for the @opentiny/vue-docs project. The dependency added is @opentiny/vue-mobile, specified with the version workspace:~. No other modifications were made to existing dependencies, scripts, or configurations within the file.

Changes

File	Change Summary
examples/sites/package.json	Added dependency @opentiny/vue-mobile with version workspace:~ in devDependencies.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant PackageManager
    participant DevDependencies

    User->>PackageManager: Request to install dependencies
    PackageManager->>DevDependencies: Check for new dependencies
    DevDependencies->>PackageManager: New dependency found: @opentiny/vue-mobile
    PackageManager->>User: Install @opentiny/vue-mobile

Loading

🐇 In the garden where bunnies play,
A new friend hops in, hip-hip-hooray!
With @opentiny/vue-mobile now here,
Our project grows, let’s give a cheer!
Dependencies bloom, oh what a sight,
Hopping along, everything feels right! 🌼

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between a9a197a and ad36e3b.

📒 Files selected for processing (1)

• examples/sites/package.json (1 hunks)

🔇 Additional comments (2)

examples/sites/package.json (2)

54-54: LGTM! Verify the dependency usage.

The addition of @opentiny/vue-mobile as a devDependency aligns with the existing mobile support in the project. The version specification workspace:~ is consistent with other @opentiny packages.

Let's verify how this dependency will be used:

✅ Verification successful

LGTM! The dependency is actively used in the mobile components.

The @opentiny/vue-mobile dependency is correctly added as it's extensively used across multiple mobile components in the examples/sites/demos/mobile/app/ directory. The search results show numerous imports of mobile components like TinyCheckbox, TinySlider, TinyUserHead, etc., from this package. The version specification workspace:~ is consistent with the monorepo setup.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for potential usage of the mobile dependency in the codebase
rg -l "@opentiny/vue-mobile" --type vue --type ts --type js

# Check if there are any mobile-specific configuration files
fd -e config.ts -e config.js -x grep -l "mobile" {}

Length of output: 227

---

Script:

#!/bin/bash
# Search for potential usage of the mobile dependency with ripgrep
rg "@opentiny/vue-mobile"

# Check the content of vite.config.ts for mobile configuration
cat examples/sites/vite.config.ts

# Look for any mobile-related files or directories
fd mobile

Length of output: 55642

---

54-54: Consider documenting mobile setup.

Since this adds to the mobile capabilities alongside existing mobile scripts and theme, consider documenting the mobile setup process.

Let's check if documentation exists:

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ 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 resolve resolve all the CodeRabbit review comments.
• @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