Skip to content

Conversation

@FliPPeDround
Copy link
Member

@FliPPeDround FliPPeDround commented Aug 4, 2025

Update dependencies

Summary by CodeRabbit

  • Chores
    • Updated several dependencies to newer versions for improved compatibility and stability. No changes to user-facing features or configuration.

@coderabbitai
Copy link

coderabbitai bot commented Aug 4, 2025

Walkthrough

This change updates development and runtime dependency versions in three package.json files across different template packages. The affected dependencies include @skiyee/uni-ui, @skiyee/ui-preset, @dcloudio/types, typescript, and vue-tsc. No other configuration, scripts, or exported/public entities were altered.

Changes

Cohort / File(s) Change Summary
Skiyee UI Template Dependency Updates
packages/core/template/UI/skiyee/package.json
Bumped "@skiyee/uni-ui" from ^0.1.1 to ^0.2.0 and "@skiyee/ui-preset" from ^0.0.4 to ^0.0.5; no other changes.
Base Template Dependency Update
packages/core/template/base/package.json
Upgraded devDependency "@dcloudio/types" from ^3.4.16 to ^3.4.19; no other modifications.
TypeScript Template Dependency Updates
packages/core/template/config/typescript/package.json
Updated "typescript" from ^5.8.3 to ^5.9.2 and "vue-tsc" from ^3.0.4 to ^3.0.5.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • chore: update deps #82: Updates dependency versions in multiple package.json files, including template/base/package.json, similar to this PR.
  • chore: update deps #116: Modifies dependency versions in the skiyee UI template, including "@skiyee/ui-preset", which is also updated in this PR.
  • chore: update deps #113: Updates dependency versions in the same package.json files within core template packages, closely matching the scope of this PR.

Poem

A hop and a skip through the package fields,
New versions sprout as the old one yields.
Types and scripts now fresh and spry,
UI shines with an updated sky.
With every bump, a smoother run—
The codebase grows, the work is done!
🐇✨

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/update-deps

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 generate unit tests to generate unit tests for 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: 0

🧹 Nitpick comments (1)
packages/core/template/UI/skiyee/package.json (1)

6-6: Keep @skiyee/ui-preset in lock-step with runtime lib

The preset normally mirrors the runtime package’s minor version. If 0.0.5 lags behind new breakpoints or colors introduced in 0.2.0, design tokens could desync.

Consider updating both to the same minor stream (e.g., 0.2.x) if available.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 2a89ce0 and 9e9e1b0.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (3)
  • packages/core/template/UI/skiyee/package.json (1 hunks)
  • packages/core/template/base/package.json (1 hunks)
  • packages/core/template/config/typescript/package.json (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (20)
  • GitHub Check: test (--ts, -e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p ...
  • GitHub Check: test (--ts, -e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p ...
  • GitHub Check: test (--ts, -e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p ...
  • GitHub Check: test (--ts, -e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p ...
  • GitHub Check: test (--ts, -e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p ...
  • GitHub Check: test (--ts, -e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p ...
  • GitHub Check: test (--ts, -e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p ...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: test (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
  • GitHub Check: stable - x86_64-pc-windows-msvc - node@20
  • GitHub Check: stable - x86_64-apple-darwin - node@20
  • GitHub Check: stable - i686-pc-windows-msvc - node@20
  • GitHub Check: stable - aarch64-pc-windows-msvc - node@20
🔇 Additional comments (3)
packages/core/template/base/package.json (1)

65-65: Confirmed single declaration of @dcloudio/types

I searched all package.json files and found only one declaration:

  • packages/core/template/base/package.json: "@dcloudio/types": "^3.4.19"

No other packages or templates reference this dependency, so all consumers are already aligned on 3.4.19. No further action needed.

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

8-9: It looks like the filter path in the dry-run command doesn’t match any package in the repo—there is no packages/core/template/base folder. To verify that TS 5.9 & vue-tsc 3.0.5 compile correctly, please run a dry build against the actual template project. For example, if the config package is at packages/core/template/config/typescript, try:

pnpm --filter ./packages/core/template/config/typescript exec tsc -p packages/core/template/config/typescript/tsconfig.json --noEmit

If that succeeds without errors, you can proceed. Otherwise, investigate any downstream plugins (e.g. unplugin-vue-macros, custom esbuild plugins) for TS 5.9 compatibility.

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

3-3: @skiyee/uni-ui 0.2.x may contain breaking style tokens

0.2.0 changelog mentions revamped component props & Tailwind token names. Verify sample pages still render and that any tree-shaken imports match the new entry points.

@FliPPeDround FliPPeDround merged commit 8cfa6c6 into main Aug 4, 2025
38 checks passed
This was referenced Sep 1, 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.

2 participants