Using pnpm@9.x based on project creation date
Unanswered
Netherland Dwarf posted this in #help-forum
Netherland DwarfOP
Hey i updated an old project on Vercel and it says this :
I checked the doc at https://vercel.com/docs/deployments/configure-a-build#corepack and added the environment variable, it fixed the error but i would like to know why Vercel is doing this based on project creation date ??
Source code and updated dependencies should take over this, no ?
I recently deployed a fresh Next.js application, using pnpm 10+ and i did not have to add the environment variable, build just went fine.
I'm a bit worried about this because what if there's other side effects that adds up as time pass ?
If someone knows here please tell me ❤️
Cheers mates, Bill.
Running build in Washington, D.C., USA (East) – iad1
Build machine configuration: 2 cores, 8 GB
Cloning github.com/Bilboramix/folio2 (Branch: main, Commit: 72e6686)
Previous build caches not available.
Cloning completed: 371.000ms
Running "vercel build"
Vercel CLI 51.6.1
Detected `pnpm-lock.yaml` 9 which may be generated by pnpm@9.x or pnpm@10.x
Using pnpm@9.x based on project creation date
To use pnpm@10.x, manually opt in using corepack (https://vercel.com/docs/deployments/configure-a-build#corepack)
Installing dependencies...
ERROR packages field missing or empty
For help, run: pnpm help install
Error: Command "pnpm install" exited with 1I checked the doc at https://vercel.com/docs/deployments/configure-a-build#corepack and added the environment variable, it fixed the error but i would like to know why Vercel is doing this based on project creation date ??
Source code and updated dependencies should take over this, no ?
I recently deployed a fresh Next.js application, using pnpm 10+ and i did not have to add the environment variable, build just went fine.
I'm a bit worried about this because what if there's other side effects that adds up as time pass ?
If someone knows here please tell me ❤️
Cheers mates, Bill.