Skip to content

Comments

chore: update deps#111

Merged
FliPPeDround merged 1 commit intomainfrom
chore/update-deps
Jun 30, 2025
Merged

chore: update deps#111
FliPPeDround merged 1 commit intomainfrom
chore/update-deps

Conversation

@FliPPeDround
Copy link
Member

@FliPPeDround FliPPeDround commented Jun 30, 2025

Update dependencies

Summary by CodeRabbit

  • Chores
    • Updated several dependency versions to ensure compatibility and improved stability, including UI component libraries and development tools. No changes to user-facing features or functionality.

@coderabbitai
Copy link

coderabbitai bot commented Jun 30, 2025

Walkthrough

This update consists of version bumps for several dependencies in various package.json files across UI templates and configuration packages. No code logic or exported/public entities were changed; only dependency versions were incremented to newer releases.

Changes

Files Change Summary
packages/core/template/UI/uni/package.json Updated "@dcloudio/uni-ui" dependency from ^1.5.7 to ^1.5.8
packages/core/template/UI/wot/package.json Updated "wot-design-uni" dependency from ^1.9.1 to ^1.10.0
packages/core/template/base/package.json Updated "@dcloudio/types" devDependency from ^3.4.8 to ^3.4.15
packages/core/template/config/lint/package.json Updated "eslint" devDependency from ^9.29.0 to ^9.30.0
packages/core/template/config/typescript/package.json Updated "@types/node" devDependency from ^24.0.3 to ^24.0.7

Possibly related PRs

Suggested labels

size/XS

Poem

A hop, a skip, a version bump,
Dependencies get over the hump.
Each package fresh, each module new,
The codebase shines in updated hue.
🐇✨
With every hop, we keep in sync,
And bugs and warnings start to shrink!


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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 7d5de39 and f3bd96a.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (5)
  • packages/core/template/UI/uni/package.json (1 hunks)
  • packages/core/template/UI/wot/package.json (1 hunks)
  • packages/core/template/base/package.json (1 hunks)
  • packages/core/template/config/lint/package.json (1 hunks)
  • packages/core/template/config/typescript/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
  • GitHub Check: stable - aarch64-apple-darwin - node@20
  • GitHub Check: stable - x86_64-apple-darwin - node@20
  • GitHub Check: build (20.x, macos-latest)
  • GitHub Check: stable - x86_64-pc-windows-msvc - node@20
  • GitHub Check: stable - i686-pc-windows-msvc - node@20
  • GitHub Check: stable - aarch64-pc-windows-msvc - node@20
  • GitHub Check: build (18.x, windows-latest)
  • GitHub Check: build (20.x, windows-latest)
🔇 Additional comments (4)
packages/core/template/UI/wot/package.json (1)

3-3: Verify wot-design-uni v1.10.0 does not introduce template-breaking changes

Minor bumps inside the same major range are usually safe, yet wot-design-uni occasionally removes/renames components between minors. Please skim the 1.10.0 release notes and make sure:

  1. No component names/props used by the starter templates were touched.
  2. Peer-dependency ranges (Vue/UniApp) remain satisfied.

If everything lines up, ship it.

packages/core/template/base/package.json (1)

64-64: Confirm @dcloudio/types 3.4.15 stays in sync with the pinned 3.0.0 runtime packages

The templates lock all runtime packages to the unusual build tag 3.0.0-4060620…, while the type stubs now float at 3.4.x. That usually works, but breaking structural changes in the .d.ts files may mis-match the generated code.

Quick manual vue-tsc --noEmit on a freshly generated project is enough to catch it.

packages/core/template/UI/uni/package.json (1)

3-3: LGTM – safe patch bump for @dcloudio/uni-ui

No red flags; minor version bump only.

packages/core/template/config/typescript/package.json (1)

6-6: Minor @types/node bump—double-check Node engine range

@types/node 24.0.7 targets Node ≈ 20/22 features. If the generated project advertises compatibility with older LTS releases (≤18), the newer typings may expose unavailable APIs in IntelliSense.

Please make sure the engines.node field (if any) aligns.

"devDependencies": {
"@uni-helper/eslint-config": "^0.4.0",
"eslint": "^9.29.0"
"eslint": "^9.30.0"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

ESLint 9 is ESM-only and still early—expect plugin breakage

Jumping from 8 → 9 is a breaking change:

• Requires Node ≥ 18
• Many community plugins/configs (including @uni-helper/eslint-config) haven’t published ESLint-9 compatible versions yet.
• ESLint 9 beta tags were released very recently.

Unless the templates have been tested end-to-end with ESLint 9, consider holding at ^8.56.0 for now.

-    "eslint": "^9.30.0"
+    "eslint": "^8.56.0"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
"eslint": "^9.30.0"
"eslint": "^8.56.0"
🤖 Prompt for AI Agents
In packages/core/template/config/lint/package.json at line 8, the ESLint version
is set to "^9.30.0", which is an ESM-only major update requiring Node ≥ 18 and
may cause plugin compatibility issues. To fix this, downgrade the ESLint version
to "^8.56.0" to maintain compatibility and stability until ESLint 9 and related
plugins are fully supported and tested.

@FliPPeDround FliPPeDround merged commit e527d00 into main Jun 30, 2025
146 of 208 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Jul 21, 2025
@coderabbitai coderabbitai bot mentioned this pull request Aug 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant