⌘K
Profile
@usernameMember since January 2020
@unitofMember since August 2024No badges yet
No accepted solutions yet
Why Vercel CLI adds itself to package.json during global version upgrades
Looks like this was addressed by https://github.com/vercel/vercel/pull/16903 . > `vercel upgrade` no longer classifies the installation as local without positive evidence (a...
Why Vercel CLI adds itself to package.json during global version upgrades
Noting that this is still happening. I just ran `vc ls` in a local NextJS repo, and after the output `vc` prompted for an upgrade. I accepted, but `vercel` added itself to...
Why Vercel CLI adds itself to package.json during global version upgrades
I actually have an old PR which I think will address this, though I had it marked as draft until just now due to an (unrelated?) test failure. Trying again:...
Why Vercel CLI adds itself to package.json during global version upgrades
It is installed globally via `npm i -g vercel`. And yes, the upgrade process I’m using is its self-updater, by accepting `y` when `vercel` detects an upgrade available, when I...
Why Vercel CLI adds itself to package.json during global version upgrades
I have `vercel` installed as a global `npm` package. Whenever I invoke a `vc` command in a repo and Vercel detects an upgrade is available, it alerts me and prompts to upgrade,...