chore: update deps

[FliPPeDround]

Update dependencies

Summary by CodeRabbit

• New Features

  • Updated dependencies to the latest versions, potentially introducing new features and improvements across various components.

• Bug Fixes

  • Minor updates to dependencies may include bug fixes and performance enhancements, ensuring a more stable user experience.

• Chores

  • Maintenance updates to development tools to improve code quality and adherence to standards.

[coderabbitai]

Walkthrough

This pull request includes minor version updates to several dependencies across different package.json files. Specifically, the versions of nutui-uniapp, wot-design-uni, and various development tools like ESLint and TypeScript-related packages have been incremented. These updates aim to ensure the project utilizes the latest features, bug fixes, and improvements from the respective libraries.

Changes

File	Change Summary
template/UI/nut/package.json	Updated nutui-uniapp from 1.7.15 to 1.7.16.
template/UI/wot/package.json	Updated wot-design-uni from 1.3.9 to 1.3.10.
template/config/lint/package.json	Updated @uni-helper/eslint-config from ^0.1.0 to ^0.2.0 and eslint from ^9.9.1 to ^9.10.0.
template/config/typescript/package.json	Updated @types/node from ^22.5.2 to ^22.5.4 and vue-tsc from ^2.1.4 to ^2.1.6.
template/module/uniUse/package.json	Updated @uni-helper/uni-use from ^0.19.12 to ^0.19.14.

Possibly related PRs

• feat: support wot-design-ui and nutui-uniapp #41: Updates nutui-uniapp from 1.7.15 to 1.7.16, related to the main PR.
• chore: update deps #51: Updates nutui-uniapp from 1.7.11 to 1.7.12, relevant to the same dependency.
• chore: update deps #56: Updates nutui-uniapp from 1.7.14 to 1.7.15, also related to the main PR.
• chore: update deps #62: Updates nutui-uniapp from 1.7.14 to 1.7.15, relevant to the same dependency.

Suggested labels

size/M

Poem

🐇 In the garden where updates bloom,
Dependencies dance, dispelling gloom.
With versions fresh, our code takes flight,
Hopping along, everything feels right!
A little fix here, a tweak over there,
Together we build, with love and care! 🌼

---

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?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1c8758b and d25c3f8.

Files selected for processing (5)

• template/UI/nut/package.json (1 hunks)
• template/UI/wot/package.json (1 hunks)
• template/config/lint/package.json (1 hunks)
• template/config/typescript/package.json (1 hunks)
• template/module/uniUse/package.json (1 hunks)

Files skipped from review due to trivial changes (5)

• template/UI/nut/package.json
• template/UI/wot/package.json
• template/config/lint/package.json
• template/config/typescript/package.json
• template/module/uniUse/package.json