Unverified50% confidenceSolutionExact time
When a project has a lockfile, even if package.json specifies ^2.0.0, installation will strictly restore the version in the lockfile and will not automatically pull 2.0.90; to get the update you need to run npm update @ai-sdk/vercel or delete the lockfile and reinstall.
1
Sources
50%
Confidence
Long-term
Relevance
10/29/2026
First Seen
Sources
Related Entities
Related Claims
Unverifiedpackage-lock.json or pnpm-lock.yaml records the resolved exact version tree; when the lockfile is unchanged, npm install will not pull new patches.78% similarUnverified版本锁定文件(package-lock.json或yarn.lock)无法完全阻断供应链攻击,因为新建项目首次安装仍会拉取被污染版本,且自动化更新工具可能升级至恶意版本78% similarUnverifiednpm install will automatically update dependencies when the lockfile is inconsistent with package.json, which may introduce untested versions.78% similarUnverifiedWhen 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.74% similarUnverifiedUsing lock files (package-lock.json or yarn.lock) can pin dependency versions and avoid inconsistency issues caused by version drift.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1112171API
curl https://kongchang.com/api/v1/knowledge/claims/1112171MCP
get_claim(id=1112171)