Maël Nison

Maybe it would be possible to ignore the mutex problem and assume that the log target would be made unique somehow (we also could provide some kind of pattern replacement,...

Sorry, I missed your RFC - we've been discussing a similar feature (optional peer dependencies) here: https://github.com/yarnpkg/yarn/issues/6487

> I didn’t even know they were strictly mandatory. I have definitely used peer dependencies as optionals, in rare cases. TIL, thanks. Peer dependencies are not strictly mandatory - it's...

I disagree - the behavior when a peer dependency is missing is clearly defined, so "you can't rely on anything working" isn't quite true. You can rely on **not** being...

> Ignoring peer dependency warnings should be a project-specific configuration, whereas `yarnrc` is meant for user-specific configuration. The yarnrc is meant for both. If you have multiple yarnrc in your...

> Going forward, I suppose `yarnrc` should be preferred for new project configuration over `package.json`? It seems safer to add things to `yarnrc` - less likely to break existing packages...

Similarly, I think I'd be more in favor of a `-Werror`-like option where warnings would be treated as errors. Would be more generic than `--enforce-peer-dependencies` or similar 😃

We should remove the globs from the documentation, they don't make sense. - `foo`: will replace any instance of `foo`, anywhere - `foo/bar`: will replace any instance of `bar` within...

I know the v1, and the behaviour you describe doesn't have the effect you think. If you use the exact same range of jQuery in two different places (like the...

I'm not sure I want to explain it works via symlinks, since it's not the case starting from PnP 🤔