fix: update template bundle (#1048)

[yy-wow]

English | 简体中文

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)
• Built its own designer, fully self-validated

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:

Background and solution

What is the current behavior?

Issue Number: N/A

What is the new behavior?

根据物料新协议更新cli模板中的bundle.json

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Added dedicated package section for @opentiny/vue and element-plus component libraries
  • Simplified package references by consolidating library information

• Refactor

  • Removed redundant versioning and script references from individual component definitions

[coderabbitai]

Walkthrough

The pull request modifies the bundle.json file in the designer template, restructuring package management for component libraries. The changes involve removing individual component versioning and script references, and introducing a new packages section that consolidates package information for @opentiny/vue and element-plus component libraries. This reorganization simplifies the package configuration by centralizing library-level details.

Changes

File	Change Summary
packages/engine-cli/template/designer/public/mock/bundle.json	- Removed individual component versioning and script references - Added new packages section - Included package details for @opentiny/vue and element-plus

Possibly related PRs

• fix: update template bundle #1048: Modifications to bundle.json file involving component library reference changes

Suggested labels

bug, refactor-main

Suggested reviewers

• rhlin
• hexqi

Poem

🐰 Bundling components with grace and might,
Versions trimmed, configuration light!
JSON dancing, libraries align,
A rabbit's refactor, simply divine!
Code simplified, packages neat,
Our bundle now looks oh-so-sweet! 🎉

---

📜 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 4e4b18e and 3d93e62.

📒 Files selected for processing (1)

• packages/engine-cli/template/designer/public/mock/bundle.json (33 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: push-check

🔇 Additional comments (3)

packages/engine-cli/template/designer/public/mock/bundle.json (3)

Line range hint 1-14038: LGTM! Component definitions are well structured.

The component definitions provide comprehensive documentation of properties, events and slots while maintaining consistency across components.

---

Line range hint 12913-14038: LGTM! Code snippets provide good examples.

The snippets are well organized by component type and provide practical examples for common use cases.

---

14039-14054: Verify package versions and consider CDN fallback strategy.

While using CDN can improve load times, consider:

1. Adding integrity hashes for the CDN scripts to prevent malicious code injection
2. Implementing a fallback mechanism in case CDN is unavailable

Let's verify the package versions are latest and secure:

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.