chore: update deps

[FliPPeDround]

Update dependencies

Summary by CodeRabbit

• Chores
  • Updated development dependencies for improved stability and compatibility, including upgrades to "@dcloudio/types", "eslint", "@types/node", and "vue-tsc".

[coderabbitai]

Walkthrough

This update increases the versions of several development dependencies in various package.json files within core templates. The changes include bumping versions for @dcloudio/types, eslint, @types/node, and vue-tsc, with no other modifications to scripts or configuration.

Changes

File(s)	Change Summary
packages/core/template/base/package.json	Updated @dcloudio/types devDependency from ^3.4.15 to ^3.4.16
packages/core/template/config/lint/package.json	Updated eslint devDependency from ^9.30.0 to ^9.30.1
packages/core/template/config/typescript/package.json	Updated @types/node from ^24.0.7 to ^24.0.10 and vue-tsc from ^2.2.10 to ^3.0.1

Possibly related PRs

• chore: update deps #109: Updates development dependencies in the TypeScript template, including @types/node, similar to this PR.
• chore: update deps #108: Bumps dependency versions in lint and typescript package.json files, focusing on devDependencies like eslint and @types/node.
• chore: update deps #106: Updates development dependency versions in lint and typescript package.json files, related to this PR's changes.

Poem

A hop and a skip, a version ascends,
Dev dependencies polished, the update extends.
Types get sharper, lint rules refined,
In the warren of code, improvements aligned.
With each little bump, the project feels new—
🐇✨ Hooray for fresh versions, from rabbit to you!

Warning

Review ran into problems

🔥 Problems

Check-run timed out after 90 seconds. Some checks/pipelines were still in progress when the timeout was reached. Consider increasing the reviews.tools.github-checks.timeout_ms value in your CodeRabbit configuration to allow more time for checks to complete.

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between e527d00 and ec6e824.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• 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. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: stable - x86_64-apple-darwin - node@20
• GitHub Check: build (20.x, macos-latest)
• GitHub Check: lint
• GitHub Check: stable - i686-pc-windows-msvc - node@20
• GitHub Check: build (18.x, windows-latest)
• GitHub Check: stable - x86_64-pc-windows-msvc - node@20
• GitHub Check: stable - aarch64-pc-windows-msvc - node@20
• GitHub Check: stable - aarch64-apple-darwin - node@20
• GitHub Check: build (20.x, windows-latest)

🔇 Additional comments (4)

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

64-64: ✅ Patch-level bump to @dcloudio/types appears safe
Version 3.4.15 → 3.4.16 is a patch upgrade; no breaking changes are expected.

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

8-8: Keep an eye on ESLint 9.30.1 release notes
Although this is only a patch, ESLint occasionally introduces rule tweaks. Make sure CI lint checks still pass in all templates after the upgrade.

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

6-6: @types/node patch upgrade is low-risk
24.0.7 → 24.0.10 should be harmless; LGTM.

---

9-9: vue-tsc major bump (2.x → 3.x) may introduce breaking diagnostics
This is a major version change. Please run pnpm run type-check (or equivalent) across all templates to verify no new type errors surface.

---

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

• 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>, 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.