chore: update deps #154
chore: update deps #154
Conversation
WalkthroughThis PR bumps dependency and devDependency versions across multiple template package.json files: uview-pro, Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes
Possibly related PRs
Suggested labels
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Tip 📝 Customizable high-level summaries are now available in beta!You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.
Example instruction:
Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later. 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. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (5)
packages/core/template/UI/uview-pro/package.json(1 hunks)packages/core/template/base/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/manifest/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). (6)
- GitHub Check: stable - aarch64-pc-windows-msvc - node@20
- GitHub Check: stable - x86_64-pc-windows-msvc - node@20
- GitHub Check: stable - i686-pc-windows-msvc - node@20
- GitHub Check: stable - x86_64-apple-darwin - node@20
- GitHub Check: stable - aarch64-apple-darwin - node@20
- GitHub Check: build (22.x, windows-latest)
🔇 Additional comments (2)
packages/core/template/base/package.json (1)
40-41: Versions exist but require manual verification for compatibility.Both package versions are confirmed to exist on npm:
@uni-helper/[email protected]and@uni-helper/[email protected]. However, no public changelog is available to document changes between versions. Notably,@uni-helper/[email protected]was published 3 days ago and carries alpha status, indicating unstable APIs. Before merging, verify that these versions work correctly in your template context, particularly the alpha version.packages/core/template/UI/uview-pro/package.json (1)
3-3: uview-pro v0.3.16 is published on npm, but lacks public release documentation.The version exists and the patch bump follows semantic versioning conventions (bug fixes only), which is a safe update pattern. However, since public release notes are unavailable, manually verify the changes before deploying to production.
| "@vue/tsconfig": "^0.8.1", | ||
| "typescript": "^5.9.3", | ||
| "vue-tsc": "^3.1.4" | ||
| "vue-tsc": "^3.1.5" |
There was a problem hiding this comment.
🧩 Analysis chain
Verify vue-tsc v3.1.5 availability.
The patch version bump from ^3.1.4 to ^3.1.5 should be safe for a type-checking tool. Verify the version exists and does not introduce any breaking changes to the type-checking behavior.
🌐 Web query:
What bug fixes are included in vue-tsc version 3.1.5?
💡 Result:
I couldn't find a release or changelog entry for vue-tsc v3.1.5. The published changelog entries I can find go up to v3.1.4 (listing its bug fixes). [1]
If you want, I can:
- check the vuejs/language-tools GitHub releases and tags for any v3.1.5 entry, or
- look up npm / unpkg / GitHub commit/PR mentions for a 3.1.5 release.
Which would you prefer?
Sources:
[1] vue-tsc changelog (package listing showing releases up to 3.1.4).
I'll verify the availability of vue-tsc v3.1.5 more directly.
Update vue-tsc version—v3.1.5 does not exist.
The latest available version of vue-tsc is 3.1.4. The specified version ^3.1.5 in the package.json will fail during package installation. Update to ^3.1.4 instead.
🤖 Prompt for AI Agents
In packages/core/template/config/typescript/package.json around line 9, the
dependency version for "vue-tsc" is incorrect (references ^3.1.5 which does not
exist); update the version string to a valid release (use ^3.1.4) in the
package.json dependency list so package installation succeeds.
| "dependencies": { | ||
| "echarts": "^6.0.0", | ||
| "uni-echarts": "^2.2.0" | ||
| "uni-echarts": "^2.2.2" |
There was a problem hiding this comment.
🧩 Analysis chain
Verify uni-echarts v2.2.2 availability.
The patch version bump from ^2.2.0 to ^2.2.2 should only include bug fixes. Verify the version exists and review what fixes or improvements are included.
🌐 Web query:
What bug fixes are included in uni-echarts version 2.2.2?
💡 Result:
I couldn't find any release notes for uni-echarts v2.2.2. The published package versions on jsDelivr/npm only list up to v2.2.0 (no 2.2.2 release or changelog available). [1][2]
Sources:
- jsDelivr uni-echarts package file list (shows latest listed v2.2.0). [1]
- jsDelivr package page for uni-echarts (version info). [2]
Remove or correct uni-echarts version reference — v2.2.2 does not exist.
The published package versions on jsDelivr/npm only list up to v2.2.0 with no 2.2.2 release available. Update the dependency to use the available v2.2.0 or verify the correct version number.
🤖 Prompt for AI Agents
In packages/core/template/module/uniEcharts/package.json around line 4, the
dependency "uni-echarts": "^2.2.2" references a non-existent release; change it
to a valid published version (e.g., "uni-echarts": "^2.2.0") or replace with the
correct version you verify, update package.json accordingly, then run npm
install (or pnpm/yarn) and confirm the lockfile and CI pass.
| { | ||
| "devDependencies": { | ||
| "@uni-helper/vite-plugin-uni-manifest": "^0.2.10" | ||
| "@uni-helper/vite-plugin-uni-manifest": "^0.2.11" |
There was a problem hiding this comment.
🧩 Analysis chain
Verify @uni-helper/vite-plugin-uni-manifest v0.2.11 availability.
The patch version bump from ^0.2.10 to ^0.2.11 should be backward compatible for a Vite plugin. Verify the version exists and contains only bug fixes with no breaking changes.
🌐 Web query:
What changes are included in @uni-helper/vite-plugin-uni-manifest version 0.2.11?
💡 Result:
I couldn't find any release notes or changelog for version 0.2.11. The publicly listed package versions for this plugin appear to go up to 0.2.8 (registry/npm listing). See the plugin docs and package info. [1][2]
Would you like me to (a) look up the package on the npm registry/GitHub again (I can fetch tags/releases), or (b) check a specific registry (e.g., your private registry) where 0.2.11 might be published?
Sources:
- Plugin docs (vite-plugin-uni-manifest). [1]
- npm package listing for related uni-helper manifest schema (shows v0.2.8). [2]
I need to investigate further since the web search indicates v0.2.11 may not exist publicly. Let me check the npm registry and GitHub repository directly.
The search results confirm a critical issue: the latest version is 0.2.9, last published a day ago, and v0.2.9 is the Latest release on GitHub. Versions 0.2.10 and 0.2.11 do not exist in the public npm registry or GitHub releases.
Update to non-existent version—npm install will fail.
The PR specifies ^0.2.11 but this version does not exist publicly. Only v0.2.9 is available. Either use ^0.2.9 or confirm the version exists in a private registry before proceeding.
🤖 Prompt for AI Agents
In packages/core/template/plugin/manifest/package.json around line 3 the
dependency version is set to "^0.2.11", but that version does not exist publicly
(latest available is 0.2.9); change the version to a valid published release
such as "^0.2.9" or confirm and point the project to the private registry that
actually hosts 0.2.11, and then update the package.json accordingly and run npm
install to verify resolution.
Update dependencies
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.