-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add ui-plugin-bundler-kit package #4916
feat: add ui-plugin-bundler-kit package #4916
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4916 +/- ##
=========================================
Coverage 56.81% 56.81%
Complexity 2971 2971
=========================================
Files 515 515
Lines 16913 16913
Branches 1273 1273
=========================================
Hits 9609 9609
Misses 6762 6762
Partials 542 542 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Ryan Wang <i@ryanc.cc>
bc96ce2
to
83feb00
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JohnNiang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
使用 Halo 新提供的 `@halo-dev/ui-plugin-bundler-kit` 包重构 Vite 打包配置。 see halo-dev/halo#4916 ```release-note None ```
使用 Halo 新提供的 `@halo-dev/ui-plugin-bundler-kit` 包重构 Vite 打包配置。 see halo-dev/halo#4916 ```release-note None ```
What type of PR is this?
/area console
/kind feature
What this PR does / why we need it:
添加
@halo-dev/ui-plugin-bundler-kit
包,用于向插件提供统一的 Vite 构建配置。最终用法:
vite.config.ts
Which issue(s) this PR fixes:
Fixes #4912
Special notes for your reviewer:
测试方式:
pnpm install path/to/halo/console/packages/ui-plugin-bundler-kit
Does this PR introduce a user-facing change?