-
-
Notifications
You must be signed in to change notification settings - Fork 20
chore: update deps #137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: update deps #137
Conversation
WalkthroughBumps versions in multiple template package.json files: UI libraries (uview-pro, wot-design-uni), TypeScript tooling (vue-tsc), and Vite plugins (@uni-helper/vite-plugin-uni-components, @uni-helper/vite-plugin-uni-pages) plus @uni-ku/root. No code, logic, or API changes. Changes
Sequence Diagram(s)Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests
Tip 👮 Agentic pre-merge checks are now available in preview!Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.
Please see the documentation for more information. Example: reviews:
pre_merge_checks:
custom_checks:
- name: "Undocumented Breaking Changes"
mode: "warning"
instructions: |
Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).Please share your feedback with us on this Discord post. 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 5
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
packages/core/template/UI/uview-pro/package.json(1 hunks)packages/core/template/UI/wot/package.json(1 hunks)packages/core/template/config/typescript/package.json(1 hunks)packages/core/template/plugin/import/package.json(1 hunks)packages/core/template/plugin/pages/package.json(1 hunks)packages/core/template/plugin/root/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). (5)
- GitHub Check: build (20.x, windows-latest)
- GitHub Check: build (20.x, windows-latest)
- GitHub Check: stable - aarch64-pc-windows-msvc - node@20
- GitHub Check: stable - i686-pc-windows-msvc - node@20
- GitHub Check: stable - x86_64-pc-windows-msvc - node@20
| "@vue/tsconfig": "^0.8.1", | ||
| "typescript": "^5.9.2", | ||
| "vue-tsc": "^3.0.7" | ||
| "vue-tsc": "^3.1.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vue-tsc@^3.1.0 resolves to no published stable version.
As of September 29, 2025 the latest stable tag is 3.0.8, while 3.1.0 only exists as the prerelease 3.1.0-alpha.0, which npm will not satisfy for the ^3.1.0 range. Installs will fail with “No matching version found”. Please stay on the 3.0.x line (e.g. ^3.0.8) until 3.1.0 ships.(classic.yarnpkg.com)
Apply this diff to keep installs green:
- "vue-tsc": "^3.1.0"
+ "vue-tsc": "^3.0.8"🤖 Prompt for AI Agents
In packages/core/template/config/typescript/package.json around line 9, the
dependency "vue-tsc": "^3.1.0" points to a non-stable prerelease that npm will
not resolve; change the version to the latest stable 3.0.x (for example
"^3.0.8") so installs succeed, then run your package manager (npm/yarn/pnpm) to
update lockfiles and verify installs.
| { | ||
| "devDependencies": { | ||
| "@uni-helper/vite-plugin-uni-pages": "^0.3.15" | ||
| "@uni-helper/vite-plugin-uni-pages": "^0.3.17" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
vite-plugin-uni-pages ^0.3.17 isn’t on npm
As of September 29, 2025 the latest published version is 0.3.2, so requesting ^0.3.17 will cause installs to error out. Please wait for 0.3.17 to be released or target an available version. (npmjs.com)
🤖 Prompt for AI Agents
In packages/core/template/plugin/pages/package.json around line 3, the
dependency version constraint "@uni-helper/vite-plugin-uni-pages": "^0.3.17"
references a non-published release and will break installs; change it to an
available published version (for example "^0.3.2" or an exact "0.3.2") or to a
compatible range that only includes published versions, then run npm/yarn
install to verify resolution succeeds.
| { | ||
| "devDependencies": { | ||
| "@uni-ku/root": "^1.4.0" | ||
| "@uni-ku/root": "^1.4.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Version ^1.4.1 isn’t published yet
npm still lists @uni-ku/root 1.3.4 as the most recent release (checked September 29, 2025), so upgrading to ^1.4.1 will break installs. Please pin to an available version (e.g., remain on ^1.3.x) or wait until 1.4.1 actually ships. (npmjs.com)
🤖 Prompt for AI Agents
In packages/core/template/plugin/root/package.json around line 3, the dependency
"@uni-ku/root": "^1.4.1" references a version that is not published; change it
to a published version (e.g., "^1.3.x" or the exact latest published "1.3.4") so
installs won’t break, update package.json accordingly and run npm install /
update lockfile to reflect the pinned valid version.
| { | ||
| "dependencies": { | ||
| "uview-pro": "^0.1.1" | ||
| "uview-pro": "^0.2.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
uview-pro ^0.2.1 hasn’t been released
The npm metadata still tops out at the 0.0.x line (latest observed 0.0.13 on September 29, 2025). Bumping to ^0.2.1 will fail because that version doesn’t exist yet. Please stick to a published tag or postpone this bump until 0.2.1 is actually available. (socket.dev)
| { | ||
| "dependencies": { | ||
| "wot-design-uni": "^1.12.4" | ||
| "wot-design-uni": "^1.13.0" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wot-design-uni ^1.13.0 not yet available
The project’s plugin marketplace and npm listing still show 1.12.4 as the newest release (status checked September 29, 2025). Upgrading to ^1.13.0 will therefore fail until the maintainers publish that tag. Please defer this bump or keep using the latest published 1.12.x build. (ext.dcloud.net.cn)
🤖 Prompt for AI Agents
In packages/core/template/UI/wot/package.json around line 3, the dependency was
bumped to "wot-design-uni": "^1.13.0" but that tag is not published yet; change
the dependency back to the latest published 1.12.x (e.g. "wot-design-uni":
"^1.12.4") or pin to the exact latest published version, and defer the ^1.13.0
bump until the maintainers publish that release.
Update dependencies
Summary by CodeRabbit