Yarn 2 is released
Hooray
Unfortunately it's quite different from npm and as a maintainer of open source code who doesn't like to force contributors to use the non-default tool, I just can't get myself to use it
Things in here are issues for mehttps://next.yarnpkg.com/advanced/migration …
-
-
Odgovor korisniku/ci @kentcdodds
yikes. wow. hopefully teams using yarn won’t put weird yarny stuff in their package.json dependencies. a schism in the ecosystem of yarn-only projects would be bad. whether intentional or not, it seems to be positioning itself as a pkg manager for *applications*, yeah?
0 proslijeđenih tweetova 8 korisnika označava da im se sviđa -
Odgovor korisnicima @b0neskull @kentcdodds
Ironically I have the opposite take. By enforcing dependencies strictness we intend to level the field by ensuring a common experience.
1 reply 0 proslijeđenih tweetova 7 korisnika označava da im se sviđa -
Now if you mean "oh hey there is a patch protocol, what if people use it", I guess my answer would be that Yarn and npm already have slightly different protocols and distributable packages just avoid them.
0 proslijeđenih tweetova 0 korisnika označava da im se sviđa
Finally just look at history: the only thing that has been causing compatibility issues with npm in the past have been different hoisting rules, never the `link:` protocol. And that's what we are fixing with predictable guaranteed.
Č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.
, your friendly package manager next door. Senior engineer 