feat: add build step to tiny-engine package

[chilingling]

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?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• New Features

  • Added dark and light theme dependencies to improve user interface customization.

• Bug Fixes

  • Corrected asset and style paths in configuration files to ensure proper loading of resources.

• Chores

  • Updated build scripts and dependencies in various package.json files for better build management and performance.

• Refactor

  • Adjusted paths in export configurations to enhance module resolution and build processes.

• Style

  • Commented out unused import statements and added placeholders for future enhancements.

[coderabbitai]

Warning

Review failed

The pull request is closed.

Walkthrough

This update includes various modifications across multiple files to improve the project's configuration and dependencies. Key changes involve updating script paths, adding new theme dependencies, adjusting Vite configuration settings, and refining build scripts. These updates enhance the project's structure, streamline theme integration, and optimize the build process.

Changes

File/Path	Change Summary
designer-demo/canvas.html	Updated the src attribute of a <script> tag from ./src/canvas.js to /src/canvas.js.
designer-demo/package.json	Added @opentiny/tiny-engine-theme-dark and @opentiny/tiny-engine-theme-light as new dependencies.
designer-demo/vite.config.js	Adjusted paths for icon directories and theme styles within the configuration.
packages/build/vite-config/package.json	Modified the build script to an empty string, removing the previous vite build command.
packages/design-core/package.json	Updated export paths to the dist directory, added a build script, and introduced new dev dependencies for ESBuild plugins.
packages/design-core/src/preview/src/main.js	Commented out an import statement for SVG icons and added a placeholder for a future theme import statement.
packages/design-core/vite.config.js	Introduced a new Vite configuration file with settings for plugins, optimization, and build output configurations.

Poem

In the land of code, changes bloom,
Themes of dark and light consume,
Paths adjusted, scripts refined,
Building stronger, intertwined.
A rabbit hops with joy and cheer,
For progress made, the future clear.
🌟

---

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.