Verified75% confidenceFactExact time
In 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 interoperate
3
Sources
75%
Confidence
Long-term
Relevance
10/30/2026
First Seen
Sources
Related Entities
Related Claims
Unverified@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.80% similarVerifiedIf the versions of @ai-sdk/vue and ai in a project are not aligned, type mismatches or runtime behavior differences may occur.78% similarUnverifiedIn a monorepo, if the ai version range declared by an adapter package does not match the version actually installed in the project, npm may install multiple copies of ai into node_modules, causing type conflicts or runtime inconsistencies.78% similarUnverifiedWhen @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.78% similarUnverifiedWhen a project depends on multiple AI SDK adapter packages at the same time, the package manager may resolve multiple copies of the same toolkit, leading to type mismatches or behavioral differences, so checking the lock file and dependency tree is especially important during upgrades.78% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1117106API
curl https://kongchang.com/api/v1/knowledge/claims/1117106MCP
get_claim(id=1117106)