3 ms·
Most of my issues were solved with 5.3.0 as of 8e979bf80. [0] >= 5.0 && < 5.3.0 were really messy and causing lots of problems for my dependencies with peer de
by jarvelov 9y ago
Most of my issues were solved with 5.3.0 as of 8e979bf80. [0]
>= 5.0 && < 5.3.0 were really messy and causing lots of problems for my dependencies with peer dependencies. And on top of that there were the issues with the lock file causing incomplete installs.
Since 5.3.0 it's been reliable for me. I've stopped using yarn altogether after it just because it's yet another installation to manage. Although the build times are much better still with yarn, but npm is making some progress with every release.
[0] https://github.com/npm/npm/commit/8e979bf80fb93233f19db003f08443e26cfc5e64 https://github.com/npm/npm/commit/8e979bf80fb93233f19db003f0...
- smt88 9y ago5.4 has major regressions and was a hellish nightmare for me for a while. I'm stuck on 5.3 now, too. I can't believe such a major tool is so poorly tested.
- Wintamute 9y agoI'm sticking with yarn for the time being I think. It feels years ahead of npm at the moment. Speed and robustness/correctness are much better, but stuff like `yarn upgrade-interactive` is also huge, also the workspaces feature.