4 ms·

> Now, the JS community seems to be thinking more about stability and backwards compatibility. That's very welcome, at least from the perspective of this grumpy

> Now, the JS community seems to be thinking more about stability and backwards compatibility. That's very welcome, at least from the perspective of this grumpy server-side developer. That's exactly why the blog post suggests using yarn instead of npm, isn't it?

lucideer 10y ago
Have you used yarn? Do you know what it is? It's a fully backwards compatible client built on the npm packaging system, using npm's repository, and built in collaboration with the npm team.
- noir_lord 10y ago
  Its also awesome, I switched when it was on HN a while back and its been amazing. I seldom get excited about JS tools but yarn is an exception.
  - boobsbr 10y ago
    Have you tried PNPM or IED?
- gcd 10y ago
  It's not quite ready for production yet. There are still some bugs with dev dependencies and private repos that need to be addressed before we can use it.