chore: update deps

[FliPPeDround]

Update dependencies

Summary by CodeRabbit

• Chores
  • Updated dependency versions across template modules for stability and compatibility improvements.

[coderabbitai]

Walkthrough

This PR updates dependency versions across multiple template package.json files, including bumps to UI libraries (nutui-uniapp, uview-pro), dev tools (TypeScript types, vue-tsc), echarts modules, and Vite plugins. No logic or control flow modifications.

Changes

Cohort / File(s)	Change Summary
UI Templates packages/core/template/UI/nut/package.json, packages/core/template/UI/uview-pro/package.json	Bumped nutui-uniapp from ^1.9.3 to ^1.9.4 and uview-pro from ^0.3.12 to ^0.3.15
TypeScript Config packages/core/template/config/typescript/package.json	Updated @types/node from ^24.10.0 to ^24.10.1 and vue-tsc from ^3.1.3 to ^3.1.4
Module Dependencies packages/core/template/module/uniEcharts/package.json	Bumped uni-echarts from ^2.1.1 to ^2.2.0
Vite Plugins packages/core/template/plugin/componentPlaceholder/package.json, packages/core/template/plugin/pages/package.json	Updated @binbinji/vite-plugin-component-placeholder from ^0.0.12 to ^0.0.13 and @uni-helper/vite-plugin-uni-pages from ^0.3.21 to ^0.3.22

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• All changes are homogeneous dependency version bumps across multiple package.json files
• No logic, control flow, or API modifications
• Consistent pattern repeated across six files

Possibly related PRs

• #145: Performs dependency bumps in the same package.json files across template packages
• #149: Updates dependency versions in overlapping template files (uview-pro, config/typescript, module/uniEcharts)
• #127: Modifies identical package.json files and bumps the same dev-dependencies (vue-tsc, @types/node, @uni-helper/vite-plugin-uni-pages)

Suggested labels

size/M

Poem

🐰 Dependencies dance in the template files,
Version bumps line up for miles,
From nutui to echarts they climb,
Patch by patch, keeping up with time!
Tiny updates, big stability—
Let them flow with agility! 📦✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore: update deps' directly and clearly summarizes the main change: updating dependencies across multiple package.json files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• 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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

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 2ba228e and 7b0de01.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (6)

• packages/core/template/UI/nut/package.json (1 hunks)
• packages/core/template/UI/uview-pro/package.json (1 hunks)
• packages/core/template/config/typescript/package.json (1 hunks)
• packages/core/template/module/uniEcharts/package.json (1 hunks)
• packages/core/template/plugin/componentPlaceholder/package.json (1 hunks)
• packages/core/template/plugin/pages/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 (-e, -p import -p pages -p layouts -p manifest -p filePlatform -p platformModifier -p middle...
• 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 (--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: stable - i686-pc-windows-msvc - node@20
• GitHub Check: stable - x86_64-apple-darwin - node@20
• GitHub Check: stable - x86_64-pc-windows-msvc - node@20
• GitHub Check: stable - aarch64-apple-darwin - node@20
• GitHub Check: stable - aarch64-pc-windows-msvc - node@20

🔇 Additional comments (6)

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

6-6: @types/node version 24.10.1 is confirmed available.

The version 24.10.1 is the latest published version as of Nov 17, 2025, published on Nov 11, 2025. This is a safe, patch-level type definition update with no runtime impact.

---

9-9: vue-tsc ^3.1.4 is available and safe to update.

Version 3.1.4 is an official release containing bug fixes for language service improvements, including HTML snippet handling, interpolation processing, and directive comment handling. This patch-level update introduces no breaking changes and is safe for the devDependency.

packages/core/template/plugin/pages/package.json (1)

3-3: Verify @uni-helper/vite-plugin-uni-pages version availability and compatibility.

Web search results confirm the package exists with 65 published versions, but specific information about version 0.3.22 (release details, breaking changes between 0.3.21→0.3.22) could not be found in publicly available sources. The npm registry may have this version, but changelog entries or release notes are not readily accessible.

Confirm:

• Version 0.3.22 is published and available on npm registry
• No breaking changes exist relative to 0.3.21

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

3-3: nutui-uniapp v1.9.4 verified.

Version 1.9.4 exists on npm registry and has no known security vulnerabilities. This patch-level bump from 1.9.3 is conservative and safe.

packages/core/template/module/uniEcharts/package.json (1)

4-4: uni-echarts version 2.2.0 is available and compatible.

The package version ^2.2.0 exists on npm as the latest release and is compatible with echarts ^6.0.0. The minor version bump from 2.1.1 to 2.2.0 maintains peer dependency compatibility (requires echarts >=5.3.0).

packages/core/template/UI/uview-pro/package.json (1)

3-3: uview-pro ^0.3.15 is a valid, recently published version with no known security vulnerabilities.

Verification confirms:

• Version 0.3.15 exists on npm (latest dist-tag, published 2025-11-14)
• Changelog shows only feature additions (nested form validation, u-dropdown enhancements) and bug fixes (u-root-portal fix in v0.3.13), with no breaking changes between v0.3.12 and v0.3.15
• No known CVEs or security advisories found
• The dependency upgrade is safe to proceed with

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

Verify @binbinji/vite-plugin-component-placeholder compatibility.

Confirm that @binbinji/vite-plugin-component-placeholder version ^0.0.13 is available. This is an early-stage package (0.0.x), so verify there are no breaking changes in this patch bump.

---

🌐 Web query:

@binbinji/vite-plugin-component-placeholder npm package version 0.0.13

💡 Result:

I couldn't find a published 0.0.13 for @binbinji/vite-plugin-component-placeholder on the npm registry. The package's latest published version appears to be 0.0.12. [1][2]

Sources:

• Socket.dev package page (shows latest 0.0.12). [1]
• Libraries.io / npm index (lists 0.0.12 as latest). [2]

---

Downgrade @binbinji/vite-plugin-component-placeholder to 0.0.12 or verify version.

Version 0.0.13 of @binbinji/vite-plugin-component-placeholder does not exist on npm; the latest published version is 0.0.12. Update the version in packages/core/template/plugin/componentPlaceholder/package.json line 3 to "^0.0.12" or confirm if 0.0.13 was intended to be published.

🤖 Prompt for AI Agents

In packages/core/template/plugin/componentPlaceholder/package.json around line
3, the dependency on "@binbinji/vite-plugin-component-placeholder" is set to
"^0.0.13" which does not exist on npm; change the version string to "^0.0.12" or
confirm and update to the correct published version, then run a quick install
(npm/yarn/pnpm) to verify resolution and update lockfile if needed.