Unverified50% confidenceFactExact time
When @ai-sdk/tool-bash bumps ai to 7.0.170 while other parts of the project still depend on ai@7.0.150, the package manager may install two copies, leading to type inconsistency or split singleton state.
1
Sources
50%
Confidence
Long-term
Relevance
11/11/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedIn npm's flattened dependency tree, if the version ranges of @ai-sdk/tui and the ai package directly depended on by the project do not overlap, the package manager may install two copies of ai, resulting in type mismatches, failed instance checks, or streaming objects that cannot interoperate78% similarVerifiedIf the versions of @ai-sdk/vue and ai in a project are not aligned, type mismatches or runtime behavior differences may occur.76% similarVerifiedAI SDK uses semantic versioning (SemVer) in the format MAJOR.MINOR.PATCH, and the @ai-sdk/vue adapter layer's version number maintains the same incremental pace as the core ai package.74% similarUnverified@ai-sdk/vue declares ai as a peer dependency, and when the two versions are inconsistent, npm or pnpm may install multiple copies of the ai package, leading to type mismatches, broken reactive state, or even runtime errors.73% similarUnverifiedThe version numbers of AI SDK adapter packages (5.x) and the major version number of the core package ai (7.x) are inconsistent, so version numbers cannot be compared directly across packages; compatibility should be judged based on the official correspondence.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1160983API
curl https://kongchang.com/api/v1/knowledge/claims/1160983MCP
get_claim(id=1160983)