Maël Nison

I don't think we should support git repositories (they are very complex to clone / install / pack), but it'd imo be reasonable to allow arbitrary urls (either `.tgz` or...

They could still easily call `--version` to know this information though.

Note that someone mentioned a bug when used with the 4.0: https://github.com/yarnpkg/berry/issues/5781#issuecomment-1755344002 (we rewrote the command to use a different npm endpoint, which unfortunately doesn't return the same data; you...

Fwiw this issue should rather be called "PnP support", since Yarn 2+ can install classical `node_modules` trees as well - it's just quite slower and suffers from the same issues...

> I would expect yarn to ignore this check in the case of `packageManager` not being yarn. Why is `yarn run` being used on a pnpm project? It seems a...

Also note that this also kinda matches how Corepack itself works: calling any pnpm command on a Yarn project yields an error, and the other way around (unless `COREPACK_ENABLE_STRICT=0` is...

There's something strange I need help understand. This message is only supposed to show up if all of those [conditions](https://github.com/yarnpkg/yarn/blob/v1.22.21/src/cli/index.js#L292-L295) are true: - There is no `yarnPath` setting - There...

Running your example with the `--progress=plain` flag, it shows the situation I described, where `yarn test` was accidentally performed by 1.22, not the version you had defined in your `packageManager`...

I still find it odd that you define a `packageManager` field but don't care that it's actually respected. Why do you have it at all?

> Anything that's yarn based is not in the PNPM workspace yet and therefore should not care about any package manager declarations above the project. It makes sense, but in...