fix(runtime): fix the problem of simple-runtime relying on echarts, and add base-select component

[zzcr]

fix(runtime): 修复simple-runtime依赖echarts问题，并补充base-select组件

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: #2685 #2064

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features
  • Introduced a new set of chart components prefixed with Huicharts, replacing previous chart components.
  • Added 24 new chart types, including HuichartsBar and HuichartsLine.
• Chores
  • Updated the version of the @opentiny/vue-runtime package from 3.20.3 to 3.20.4.

[coderabbitai]

Walkthrough

The pull request modifies the build-entry-app.ts file by updating the notSimpleComponents array. It removes 24 chart-related components, such as Chart and ChartBar, and replaces them with a new set of components prefixed with Huicharts, including HuichartsBar and HuichartsLine. This change updates the components excluded in simple mode, focusing solely on the transition from the previous chart components to the new Huicharts components while maintaining the overall structure and logic of the buildFullRuntime function.

Changes

File	Change Summary
internals/cli/src/commands/build/build-entry-app.ts	Removed 24 chart-related components from notSimpleComponents and added new Huicharts prefixed components.
packages/vue-runtime/package.json	Updated version of @opentiny/vue-runtime from 3.20.3 to 3.20.4.

Possibly related PRs

• build(charts): compatible with the old version of charts chart introd… #2327: Modifies build-entry-app.ts file, specifically the buildFullRuntime function, related to component handling.
• fix(chart): huiCharts打包替换为Chart #2622: Focuses on the replacement of 'Huicharts' with 'Chart', aligning with the main PR's changes.
• fix(chart): modify chart packages #2354: Discusses modifications to chart packages, relevant to the context of chart components.
• build(runtime): fix runtime build error and remove useless svg-icon c… #2357: Includes changes to build-entry-app.ts, specifically removing the SvgIcon component, relevant to component management.
• feat: add saas-common runtime #2700: Introduces a new feature related to the saas-common runtime, indicating ongoing enhancements in the build process.

Suggested labels

enhancement

Poem

🐰 Hop, hop, through components we go,
Charts renamed with a magical glow.
HuiCharts dancing, old names fade away,
Building runtime in a brand new way!
Rabbit's code magic never astray 🎨

---

📜 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 29a3b32 and d6c94de.

📒 Files selected for processing (1)

• packages/vue-runtime/package.json (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• packages/vue-runtime/package.json

---

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.

[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