Unverified50% confidenceFactExact time
In downstream projects, if an older version of provider-utils is pinned, the package manager may retain the old version when installing @ai-sdk/typesafe-ai@3.0.40 to satisfy the range constraints of other dependencies, resulting in version splits.
1
Sources
50%
Confidence
Long-term
Relevance
11/13/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen provider-utils is upgraded but the package.json of @ai-sdk/voyage still specifies a looser range (such as ^4.0.60) and the lockfile is not refreshed, the version actually installed may be an old provider-utils, causing a version mismatch problem.78% similarUnverifiedIf a project pins a newer @ai-sdk/provider-utils but still uses an older @ai-sdk/zai, upgrading @ai-sdk/zai is worthwhile; conversely, if the dependency tree has an older provider-utils version, upgrading zai alone is of little value.76% similarUnverifiedEven if the version declaration of @ai-sdk/xai allows upward compatibility, as long as the lock file is not updated, the actually installed @ai-sdk/provider-utils may still be an old version; only running commands such as npm update will truly rewrite the lock file and pull the new version.76% similarUnverified使用 @ai-sdk/xai 调用 Grok 模型的项目建议跟随升级,锁死旧版 provider-utils 的风险通常不在 xAI 调用本身,而在与其他 @ai-sdk/* 包共存时出现的依赖版本漂移。75% similarUnverifiedIf only the provider side is upgraded while the ai package version is too old, type mismatches may occur.75% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1166439API
curl https://kongchang.com/api/v1/knowledge/claims/1166439MCP
get_claim(id=1166439)