Use current yarn version on deploy to vercel

[rin-st]

Description

Copying behaviors from #998

Current Behavior

deployment log from main branch

...
Running "vercel build"
Vercel CLI 39.1.1
Running "install" command: `yarn install`...
yarn install v1.22.19
info No lockfile found.
...

So our yarn.lock file is ignored and the last version will be installed when we have ^x.y.z versions of packages. It can cause errors

Expected Behavior

yarn version 3.2.3 should be used
yarn.lock should be used

---

Since our yarn.lock is located at the root of the repo, I think we can't use locked versions of nextjs package on our deploys. But it's possible at least to change yarn version to 3.2.3 from ^1. I'm still not sure if it adds a lot of value but I think it could solve some issues we had before when using yarn v1 or other incompatible yarn versions.

So, to use current version on deploy to vercel we need to add to package.json

• packageManager
• ENABLE_EXPERIMENTAL_COREPACK=1 to enable use of packageManager docs
• YARN_ENABLE_IMMUTABLE_INSTALLS=false to enable creating new yarn.lock on deploy. I don't see it in the docs, but this helped to prevent this error:

Vercel CLI 39.1.3
> Detected ENABLE_EXPERIMENTAL_COREPACK=1 and "[email protected]" in package.json
Running "install" command: `yarn install`...
➤ YN0028: The lockfile would have been created by this install, which is explicitly forbidden.
➤ YN0000: Failed with errors in 0s 4ms
Error: Command "yarn install" exited with 1

---

Resulting build logs:

Running "vercel build"
Vercel CLI 39.1.3
> Detected ENABLE_EXPERIMENTAL_COREPACK=1 and "[email protected]" in package.json
Running "install" command: `yarn install`...
➤ YN0000: ┌ Resolution step
...

and it builds with no errors

Fixes #998

Additional Information

• I have read the contributing docs (if this is your first contribution)
• This is not a duplicate of any existing pull request

[technophile-04]

Noiceee catch! And agree that it's more reliable to use yarn v3 with vercel clil deployment too!

I think it's fine we use "experimental" flag ENABLE_EXPERIMENTAL_COREPACK since maybe corepack is already being used a lot? and also if nodejs removes we would easily know the news remove that flag 🙌 Thanks @rin-st nice improvement!