bkamrani
(Bkamrani)
May 15, 2025, 5:24pm
1
Why am I still not upgrading to the latest Vercel even after this command?
npm i -g vercel@latest
And get this warning:
╭──────────────────────────────────────────────────────────╮
│ │
│ Update available! v34.2.7 ≫ v41.7.4 │
│ Changelog: Releases · vercel/vercel · GitHub │
│ Run npm i -g vercel@latest
to update. │
│ │
╰──────────────────────────────────────────────────────────╯
I have also run the command with sudo
as well as npm cache clean -f
FYI,
which vercel && node --version && npm --version
/usr/local/bin/vercel
v23.10.0
10.5.0
Many thanks!
anshumanb
(Anshuman Bhardwaj)
May 16, 2025, 8:33am
3
Hi @bkamrani , welcome to the Vercel Community!
Sorry that you’re facing this issue. Have you tried clean installing the vercel
CLI?
npm uninstall -g vercel
npm cache clean -f
npm i -g vercel@latest
Also, are you using NVM to manage multiple versions of Node?
bkamrani
(Bkamrani)
May 16, 2025, 9:02am
4
I tried but it didn’t work. There seemed to be two installations (one global and local) which messed up things. I was eventually able to resolve it by totally delete everything by force and re-install. Something like:
sudo npm uninstall -g vercel # Uninstall
sudo rm -rf /usr/local/lib/node_modules/vercel # Delete residual files
sudo rm /usr/local/bin/vercel # Remove symlink
npm cache clean -f # Clear cache
Reinstall Vercel Fresh
sudo npm install -g vercel@latest --force
# --force bypasses cache
Please feel free to close. Thanks!
1 Like
anshumanb
(Anshuman Bhardwaj)
May 16, 2025, 9:03am
5
I’m glad you got this working. Yeah, two installations is a very common issues with -g
option.
Thanks for sharing your solution with the community.