-
Notifications
You must be signed in to change notification settings - Fork 168
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 element-plus
& uplugin-*
& vite-plugin-*
& @vueuse
#95
Conversation
Warning Rate limit exceeded@fengmk2 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 48 minutes and 59 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. WalkthroughThe Changes
Poem
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
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.
Actionable comments posted: 0
Outside diff range and nitpick comments (6)
package.json (6)
127-127
: Consider specifying more specific version ranges for@vueuse
,@vuepress
,@waline
,@wangeditor
to avoid potential issues with major updates.
173-173
: Consider specifying a more specific version range for@sxzz
to ensure stability.
4860-4862
: Consider specifying a more specific version range forelement-plus
to ensure stability.
16314-16352
: Consider specifying more specific version ranges for allunplugin-*
packages to ensure stability.
16782-16787
: Consider specifying more specific version ranges forvite-ssg
andvite-ssg-sitemap
to ensure stability.
16854-16871
: Consider specifying more specific version ranges forvite-plugin-webfont-dl
,vite-plugin-vue-devtools
,vite-plugin-vue-layouts
, andvite-plugin-pwa
to ensure stability.
element-plus
& uplugin-*
& vite-plugin-*
& @vueuse
element-plus
& uplugin-*
& vite-plugin-*
& @vueuse
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.
+1
[skip ci] ## [1.47.0](v1.46.0...v1.47.0) (2024-06-02) ### Features * Add "iview-area-wx" ([#94](#94)) ([4aceca5](4aceca5)) * add `element-plus` & `uplugin-*` & `vite-plugin-*` & `[@vueuse](https://github.com/vueuse)` ([#95](#95)) ([06dcb09](06dcb09)) * add fomantic-ui ([#97](#97)) ([58f2288](58f2288)) * add js-asuna ([#98](#98)) ([a5ca7ce](a5ca7ce)) * add twikoo ([#93](#93)) ([0b54718](0b54718)) * add vuetify and @mdi/font ([#99](#99)) ([b4fcf5b](b4fcf5b))
Summary by CodeRabbit