Interesting. I've never considered Yarn non-default. At least in the react-native community it's default.
-
-
-
When you install node, npm comes in. Have an extra step to get yarn.
- Još 3 druga odgovora
Novi razgovor -
-
-
Ouch. I understand switching to yarn just for an npm-like replacement, but forcing VSCode users to do a special extra step? That's a hard no
- Još 2 druga odgovora
Novi razgovor -
-
-
Hm, why this one is controversial to u? Seems pretty reasonable to me, using npm-named file to configure stuff for other tool seems to be confusing in the long run.
Kraj razgovora
Novi razgovor -
-
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?
-
Ironically I have the opposite take. By enforcing dependencies strictness we intend to level the field by ensuring a common experience.
- Još 2 druga odgovora
Novi razgovor -
-
-
I don't get why they've done it? I can't find a "these are the benefits of yarn 2" page?
- 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.
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 me