Maël Nison
Maël Nison
> yarn add -P coraline@https://github.com/Pnlvfx/coraline.git > > then yarn will not install it but just add it on the peer dependencies as: > > "peerDependencies": { "coraline": "https://github.com/Pnlvfx/coraline.git" }, It...
> Maybe we can do that, or use `latest` as a fallback? I think it'd make sense to tolerate the prerelease versions until at least one stable is released. We...
That's what I'm thinking, yes
The current alternative is to use `yarnPath`, but we're discussing adding `packageManager` support to the `yarn` npm package, so that users can either use `npm install -g corepack` or `npm...
I'm a little hesitant to make this change in Yarn since this warning is a client-side message that a third-party tool emits (`yarn npm publish` doesn't). Yarn sends the same...
Yes, but that's not the only change we perform. For instance we also normalize the `dependencies` map to sort everything. If we were to try to preserve the initial style...
Yes, because the implicit bin name is always the package name without its scope (otherwise the slash would make it impossible to add to the PATH).
Fwiw I'm -1 on merging something in the 3.x branch that isn't a straight cherry-pick from master. I can imagine a change like this changing some edge case behaviour somewhere,...
> and I believe it's neither here nor there Sure it is. You're asking us to ship code exclusive to the 3.x branch, which we don't dogfood anymore, and possibly...
I don't feel like there's enough value in making those configurable that it's worth the maintenance/complexity cost.