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

  • Centralized package management by introducing a new packages section in the configuration
  • Added explicit package references for TinyVue and Element Plus component libraries

• Refactor

  • Simplified component definitions by removing redundant package information from individual component entries

[coderabbitai]

Walkthrough

The pull request modifies the bundle.json file in the designer template, restructuring how component library packages are defined. The changes involve removing individual component-level package references and introducing a new centralized packages section that consolidates package information for TinyVue and Element Plus component libraries. This refactoring simplifies the JSON structure by moving version and script URL details to a dedicated section.

Changes

File	Change Summary
packages/engine-cli/template/designer/public/mock/bundle.json	- Removed individual npm package references for Element Plus and TinyVue components - Added new packages section with centralized library information - Defined package details for TinyVue组件库 and element-plus组件库

Possibly related PRs

• fix: update template bundle #1048: Similar modifications to the bundle.json file involving component library package reference restructuring

Suggested reviewers

• rhlin
• chilingling

Poem

🐰 Bundling libraries with care and grace,
Refactoring JSON at a rabbit's pace
Versions and scripts now neatly aligned
In packages section, perfectly designed
A cleaner structure, oh what delight! 🎉

---

📜 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 336dd68.

📒 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 (1)

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

14039-14054: Verify package versions and security advisories.

The package configuration has been nicely consolidated into a dedicated packages section. However, we should verify:

1. That the specified versions exist and are secure
2. Any known vulnerabilities in these versions

✅ Verification successful

Package versions are secure and properly configured

The specified versions (TinyVue 3.14.0 and Element Plus 2.4.2) are free from known vulnerabilities. While newer versions exist, using stable older versions is a common practice. The CDN configuration through unpkg.com follows standard practices.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for security advisories and latest versions of the packages

# Check PyPI for latest versions
echo "Checking latest versions..."
curl -s https://registry.npmjs.org/@opentiny/vue/latest | jq '.version'
curl -s https://registry.npmjs.org/element-plus/latest | jq '.version'

# Check for security advisories
echo "Checking security advisories..."
gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NPM, package: "@opentiny/vue") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}
'

gh api graphql -f query='
{
  securityVulnerabilities(first: 5, ecosystem: NPM, package: "element-plus") {
    nodes {
      advisory {
        summary
        severity
        publishedAt
      }
      vulnerableVersionRange
      firstPatchedVersion {
        identifier
      }
    }
  }
}
'

Length of output: 1230

---

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.