Improve Yarn berry support

[JGAntunes]

This is a cover issue to track problems our build system has with Yarn 2/3. Specifically:

• Inability to retain Yarn's own cache - Yarn arguments #319, Fix support for Yarn 2 (berry) #465 and Yarn fetches all packages on every build (cache issue) #600
• Pointless installs of yarn are always triggered due to the mismatch caused by the yarn-path configuration property - yarn-path configuration property forces needless yarn binary installs #594
• Yarn v3 issue when installing plugins: Yarn v3 does not work with Build plugins build#3650

[ehmicky]

Note: related issue on netlify/build: netlify/build#1535

[mauriciabad]

Is there any progress on this? 😊 I'm also having this issue.

[jasikpark]

I'd love to see this fixed to reduce build times for my sites!

[rmcfadzean]

I'm not sure where I saw it on github and it isn't my favourite way but this works in a pinch until it's better supported out of the box:

[build.environment]
YARN_ENABLE_GLOBAL_CACHE = "true"
YARN_GLOBAL_FOLDER = "/opt/buildhome/.yarn_cache"

Add that to your netlify.toml.

➤ YN0000: ┌ Fetch step
➤ YN0013: │ 4 packages were already cached, 2089 had to be fetched
➤ YN0000: └ Completed in 1m 58s

Became:

➤ YN0000: ┌ Fetch step
➤ YN0013: │ 2089 packages were already cached
➤ YN0000: └ Completed in 536ms

[marcofugaro]

We are wasting precious netlify build minutes.
Would love to see some progress on this as well.

[marcofugaro]

Thanks @rmcfadzean, your solution works wonderfully for now!

[jesse-holden]

Can confirm solution provided by @rmcfadzean also works for monorepos that use a custom base directory, am now saving an average of 2 minutes on each build since using this fix

[robations]

I don't know if this needs a separate issue but I get the following error with "@netlify/plugin-functions-install-core" (yarn 3.0.2):

Error while installing dependencies in /opt/build/repo/functions
Unknown Syntax Error: Unsupported option name ("--no-progress").

$ yarn install [--json] [--immutable] [--immutable-cache] [--check-cache] [--inline-builds] [--mode #0]

Plugin details
Package:        @netlify/plugin-functions-install-core
Version:        18.17.2
Repository:     git+https://github.com/netlify/build.git
npm link:       https://www.npmjs.com/package/@netlify/build
Report issues:  https://github.com/netlify/build/issues
...

I was thinking PnP would be a good solution to speed up build/deploy but seems like there's a bit of work to do. I was also weighing up pnpm, but seems like support would be patchy. Are there any sane workarounds for disabling npm/yarn and manually packaging functions? Or otherwise decoupling the package manager from build process?

One other note, I added the functions/ dir as a workspace in yarn to silence various warning errors about stray package.json files. Not sure what best practice is here.

[jonioni]

The solution mentioned above #612 (comment) doesn't seem to work anymore with Yarn v3 (#615). Is there an updated fix?

[aduh95]

Could we add to the list:

• Adding support for "packageManager" field in the package.json?
• Adding support for interacting with Yarn using Corepack (corepack yarn handles the download of the correct version instead of having to specify a version from the env variable)?

Corepack is listed as the preferred install method for Yarn according to https://yarnpkg.com/getting-started/install, but it seems it's not possible to use it with Netlify Deploys.

[kachkaev]

Seems like there is still no solution for Yarn 3 caching. I tried finding a workaround today but gave up: netlify/build#1535 (comment) HALP! 🙏

[gpoole]

Hopefully to save a bit of digging for anyone else facing this issue with Yarn v3, here's a working fix: netlify/build#1535 (comment)

The change from #612 (comment) is that the cache variable is now YARN_CACHE_FOLDER instead of YARN_GLOBAL_FOLDER as per the Yarn documentation.