4 ms·
The single decision from the Yarn team to not offer a reasonable transition path from v1 to v2 was a total blocker for my teams. After trying it on seldected p
by xcambar 5y ago
The single decision from the Yarn team to not offer a reasonable transition path from v1 to v2 was a total blocker for my teams.
After trying it on seldected projects, we collectively decided that it was not worth it to follow a project that did not take its users' time seriously, since the migration was so hard.
So, yarn@v1 then npm@v7+ for us.
- ironmagma 5y agoFrom the looks of it, the Yarn "team" is mostly one guy. Edit: I retract my previous comment, the additions/deletions count seems misleading. [1] https://github.com/yarnpkg/berry/graphs/contributors https://github.com/yarnpkg/berry/graphs/contributors
- arcatek 5y agoI was the main developer back when the 2.0 was started (so, like, rc.1), but since then we grew and are now a team, with at least four very active contributors of similar expertise. I believe this is the greatest accomplishment of the v2.
- chadlavi 5y agoYep. At least give us some utilities to convert the config files. I'm not hand re-writing all that.