fix: fix build:runtime script

[kagol]

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
  • Enhanced the build process to automatically generate essential icon components before assembling the runtime package, leading to improved asset integration.

[coderabbitai]

Walkthrough

The pull request updates the build:runtime script in the package.json file. The new command now executes pnpm create:icon-saas before running the existing runtime build command. This change ensures that the icon SaaS component is created as a prerequisite for the runtime build process.

Changes

File	Change Summary
package.json	Updated build:runtime script from "pnpm -C internals/cli build:runtime" to add pnpm create:icon-saas && before the runtime build command.

Sequence Diagram(s)

sequenceDiagram
  participant Runner as Build Runner
  participant Icon as Icon Creator
  participant Runtime as Runtime Builder
  
  Runner->>Icon: Execute "pnpm create:icon-saas"
  Icon-->>Runner: Icon component created
  Runner->>Runtime: Execute "pnpm -C internals/cli build:runtime"
  Runtime-->>Runner: Runtime built successfully

Loading

Poem

I’m a rabbit on a coding spree,
Hopping through scripts so merrily.
Icons now spring to life with a twist,
Runtime builds persist, none dismissed.
With each command, our code sings free!
🐇✨ Happy hops and code delights!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

package.json (1)

56-56: Enhanced build:runtime script with prerequisite icon SaaS creation.
The updated "build:runtime" script now invokes "pnpm create:icon-saas" before running "pnpm -C internals/cli build:runtime". This change is consistent with similar patterns used in other scripts (e.g., "dev:saas", "site:saas") and ensures that the icon SaaS component is created as a prerequisite for the runtime build process.

Please verify that:

• The create:icon-saas command does not introduce any unintended delays or side effects in environments where the icon SaaS component might have already been generated.
• The sequential execution (&&) correctly aborts the runtime build if the create:icon-saas fails.

Overall, the change aligns with the PR objectives and helps in maintaining a proper build chain.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between afd76e7 and 2e3044c.

📒 Files selected for processing (1)

• package.json (1 hunks)