Maël Nison

How so? Do you have an example of case where this wouldn't fly? (I can see one I didn't described in the RFC, the tooling need to somehow publish those...

> Well, how can you be sure that all those package names are not already occupied in the registry? Also, I can imagine a scenario where someone will publish a...

> If `prisma` has _different dependencies_ from `prisma-win32-x64` which in turn has different dependencies from `prisma-linux-ia32`, then we're in real trouble. Two installations at the same time with the same...

Thanks for the write-up! I've focused around the specific parts you mentioned as divergences; overall I think we're on the same page, and the changes you suggest seem fair to...

> Do I understand correctly, that this will allow to have only a single dependency with variants? What if several dependencies need variants? Also, what if I want variants in...

Another interesting use-case for Package Variants could be to ship translations as separate packages (`@moment/locale-%locale`), and let users define the set of languages they'd want to see installed via `dependenciesMeta`....

Hey @ruyadorno; thanks for the ping, but the [comment](https://github.com/yarnpkg/berry/issues/2751#issuecomment-841500039) you're referring to was made about a year ago. I have to say, I'm a little annoyed that you (as in,...

Optional peer dependencies are intended to be optional, so they shouldn't be installed by default (and in fact you even have [open bugs](https://github.com/npm/feedback/discussions/225#discussion-3224633) suggested you're already installing them, against their...

> For the Node core code, should there be a plan in place for when and how to update it? Usually we update whenever someone tells us something doesn't seem...

The technical challenge isn't the main hurdle, although it is certainly one. My main concern is that this goes against the current ecosystem. If every library starts forcing dependencies, it's...