Maël Nison

Hey! I think @merceyz has made some experiments, maybe they'll have more insight to share! If I remember correctly, the main issue is that part of Electron is running within...

It was inherited from Yarn 1, which I _think_ inherited it from npm: https://github.com/yarnpkg/yarn/blob/7cafa512a777048ce0b666080a24e80aae3d66a9/src/cli/commands/pack.js#L50 I don't have a very strong opinion on this - although just a small note the...

That seems like it indeed; I'm ok to remove it, but note it'll have to wait the next major, which may take some time.

> Open question: For people who had upvoted #6579, what use cases still need addressing? We have a strongly-typed filesystem library, where the user is expected to manipulate "clean types"...

> @arcanis it really sounds like you want nominal types (#202), since even if regex types existed, you'd still want the library consumer to go through the validator functions? Frankly,...

Yes, I think removing the index is fine. We're actually wrapping up the [new website](https://yarn-v4-wip-website-dont-bookmark.netlify.app/), so we can do that once it's deployed (a couple of weeks).

The Bluesky post made me curious so I dig a little more - I doubt the issue is that pnpm isn't installing `@types/estree`. This shows that the dependency is properly...

We don't plan to support non-git repositories in places where CVS are integrated. We used to consider having [some level of indirection](https://github.com/yarnpkg/berry/tree/master/packages/plugin-stage/sources/drivers) which would eventually allow implementing actions for different...

I can also confirm it fixes the issues we had at work with ESLint in VSCode when using `eslint-plugin-mdx` (I manually patched our local `synckit` package using [`yarn patch`](https://yarnpkg.com/cli/patch)). Note...

We added the missing release artifacts a couple of days ago. I don't have details on your build infra so I don't know why it'd affect the build output -...