> 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?
That's exactly why the blog post suggests using yarn instead of npm, isn't it?