Added some of my thoughts based on what I learned from working on React. Hope it can be helpful.https://github.com/yarnpkg/berry/issues/766#issuecomment-580277789 …
Prikaži ovu nit
The Yarn strict mode proposal from a chat with @arcanis, as summarized by @cpojer here, makes a lot of sense to me.https://github.com/yarnpkg/berry/issues/766#issuecomment-580222903 …
-
-
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I disagree. Shipping with PnP off by default will result in PnP never gaining adoption. I think
@arcanis had the right idea with the launch. It might be painful at first, but at least it will force libraries and tools to become compatible more quickly. -
On the other hand, shipping with PnP on by default will result in Yarn 2 never gaining adoption so either way those libraries and tools are not going to ship the improvements.
- Još 6 drugih odgovora
Novi razgovor -
-
-
What do you think that will happen about the react native projects with yarn 2 upgrade with same name?
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
I don't wholly disagree with this since it allows `yarn add` commands all over GitHub to continue working. However, making PnP opt-in makes it very likely that a minority of stragglers will hold the community back long-term.
-
Therefore, I think (1) a package's compatability should be highlighted by default, and (2) `yarn init` should default to enabling PnP when creating new projects.
Kraj razgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.