Kristoffer K.

It's still experimental so we should wait until the minimum supported version of Node.js ships with a version of Undici with stable and enabled by default support. https://github.com/nodejs/undici/blob/d61af698dc50234289621c3613be9a8e42bf8e1f/lib/dispatcher/env-http-proxy-agent.js#L26-L28 Or once...

I haven't tested it but this might fix https://github.com/yarnpkg/berry/issues/3996.

> This is intended for 3.x. I picked the closest base branch as target that I found on the repo. That would be https://github.com/yarnpkg/berry/tree/cherry-pick/next-release

> Should the first argument here have been process.execPath? It seems odd to call physicalPath directly only if falsey? Probably but that branch is dead code, `physicalPath` is never falsy...

With https://github.com/yarnpkg/berry/pull/3146 merged `pinst` should be able to remove the `postinstall` script before packing again, we could potentially support overriding lifecycle scripts in [`publishConfig`](https://yarnpkg.com/configuration/manifest#publishConfig) to have a development only `postinstall`...

> I just moved to yarn 2 and I can't find a way to update all packages at once. > Is there any way to upgrade all the deps to...

> [@yarnpkg/cli](https://ci.nodejs.org/view/Node.js-citgm/job/citgm-smoker/3527/nodes=osx11/testReport/junit/(root)/citgm/_yarnpkg_cli/) /cc @arcanis @merceyz @paul-soporan @larixer (looks like a test is broken by the unflagging of require(esm)) Thanks for the ping, should be fixed by https://github.com/yarnpkg/berry/pull/6639.

Literals are treated differently, their casing is preserved in the resulting column name.

You can avoid downloading all the packages anew by mounting a cache for the install step ```Dockerfile RUN \ --mount=type=cache,target=/root/.yarn \ yarn ``` With this cache adding a new dependency...

Some of our dependencies are using `lodash` so this would increase the install size and maybe the bundle size.