fix: fix build all components error

[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

• New Features

  • Enhanced UI component building for different Vue versions.
  • Added support for new icon tasks in the build process.

• Bug Fixes

  • Simplified CSS variable definitions in the old theme to improve styling consistency.

• Chores

  • Updated package dependencies to include @opentiny/vue-icon for better icon management.

[coderabbitai]

Walkthrough

The pull request introduces several modifications across multiple files, primarily enhancing the build process for UI components related to different Vue versions. A new design entry is added to the matchList in the build-ui.ts file, which affects how the build handles specific files. Additionally, a new dependency is included in the package.json for the @opentiny/vue-design-smb package. Changes to the CSS variable definitions in the old-theme-index.js file simplify the theme's styling by reducing the number of defined variables.

Changes

File Path	Change Summary
internals/cli/src/commands/build/build-ui.ts	- Added 'design/smb' to matchList. - Updated buildUi function to handle new icon tasks. - Modified getTasks to default to building all modules if no names are provided.
packages/design/smb/package.json	- Added dependency: "@opentiny/vue-icon": "workspace:~".
packages/theme/src/old-theme-index.js	- Modified CSS variable definitions in the tiny-old-theme object, reducing the number of variables.

Possibly related PRs

• feat: add design smb packages #2591: The addition of the @opentiny/vue-design-smb package relates to the new entry for "DesignSmb" in the commonMapping.json.
• fix(site): add smb design-config support #2599: Changes to add SMB design-config support connect to modifications in the useTheme.js file for handling designSMBConfig.
• refactor(theme-doc): add ThemeTools docs #2403: Documentation updates regarding theme tools may relate to enhancements in theme management, including new SMB design configurations.
• feat(theme): [button] submit the initial version of aurora-theme-vars #2596: Introduction of aurora-theme-vars aligns with broader theme enhancements relevant to the SMB design.
• test(e2e): [input,link,popeditor] fix input、link、popeditor error e2e test #2586: Fixes in e2e tests for input, link, and popeditor components may indirectly relate to overall stability improvements from SMB design configurations.

Suggested labels

bug

Suggested reviewers

• kagol

🐇 In the meadow where the bunnies play,
New designs hop in, brightening the day.
With icons and themes, all fresh and spry,
Building our UI, oh my, oh my!
A sprinkle of magic, a dash of delight,
Let’s celebrate changes, all fluffy and bright! 🌼✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between ac4e4cf and 30fbd84.

📒 Files selected for processing (3)

• internals/cli/src/commands/build/build-ui.ts (1 hunks)
• packages/design/smb/package.json (1 hunks)
• packages/theme/src/old-theme-index.js (1 hunks)

🔇 Additional comments (3)

packages/design/smb/package.json (1)

6-8: LGTM: Appropriate workspace dependency added

The addition of @opentiny/vue-icon as a workspace dependency is correct and follows the monorepo dependency pattern.

internals/cli/src/commands/build/build-ui.ts (1)

210-210: LGTM: Design system path added to build configuration

The addition of 'design/smb' to matchList enables the build system to process the new design system module.

Let's verify the design system path integration:

✅ Verification successful

The design system path 'design/smb' is correctly integrated in build configuration

Based on the build-ui.ts file content, I can verify that 'design/smb' is properly added to the matchList array alongside other design system paths ('design/aurora' and 'design/saas'). This list is used in the package.json generation logic to handle main and module entry points for design system packages.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Verify the design system path structure and related files

# Check if the design system directory exists and has expected structure
fd --type d "design/smb" packages/

# Check for any references to the design system in build configurations
rg -l "design/smb" "internals/cli/src/**/*.ts"

Length of output: 147

---

Script:

#!/bin/bash
# Let's verify with more precise paths and broader search

# Check if the design system directory exists anywhere in the repository
fd "design/smb"

# Search for any references to design/smb in all TypeScript files
rg -l "design/smb" "**/*.ts"

# Check the specific build configuration file content
cat "internals/cli/src/commands/build/build-ui.ts"

Length of output: 15265

packages/theme/src/old-theme-index.js (1)

5-5: LGTM: Comprehensive theme variable definitions

The CSS variables are well-structured, following consistent naming conventions and covering all necessary design aspects (colors, typography, spacing, shadows, etc.).

---

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