Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion packages/core/template/UI/uview-pro/package.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"dependencies": {
"uview-pro": "^0.3.15"
"uview-pro": "^0.3.16"
}
}
4 changes: 2 additions & 2 deletions packages/core/template/base/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -37,8 +37,8 @@
"@dcloudio/vite-plugin-uni": "3.0.0-4080520251106001",
"@mini-types/alipay": "^3.0.14",
"@uni-helper/plugin-uni": "0.1.0",
"@uni-helper/unh": "^0.2.5",
"@uni-helper/uni-types": "^1.0.0-alpha.6",
"@uni-helper/unh": "^0.2.7",
"@uni-helper/uni-types": "^1.0.0-alpha.7",
"@vue/runtime-core": "3.4.21",
"miniprogram-api-typings": "^4.1.0",
"sass": "1.64.2",
Expand Down
2 changes: 1 addition & 1 deletion packages/core/template/config/typescript/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,6 @@
"@types/node": "^24.10.1",
"@vue/tsconfig": "^0.8.1",
"typescript": "^5.9.3",
"vue-tsc": "^3.1.4"
"vue-tsc": "^3.1.5"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

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

}
}
2 changes: 1 addition & 1 deletion packages/core/template/module/uniEcharts/package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"dependencies": {
"echarts": "^6.0.0",
"uni-echarts": "^2.2.0"
"uni-echarts": "^2.2.2"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

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

}
}
2 changes: 1 addition & 1 deletion packages/core/template/plugin/manifest/package.json
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"devDependencies": {
"@uni-helper/vite-plugin-uni-manifest": "^0.2.10"
"@uni-helper/vite-plugin-uni-manifest": "^0.2.11"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

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

}
}
Loading
Loading