It is important to ensure that both your development and production environments are using the dependencies that you expect. As I’ve found before, Yarn and npm behave a little differently.

The upgrade of React to version 16 caused issues in our repos with dependencies that were relying on deprecated functionality that had now been removed.

Yarn 1.0 has been out for a while now and in the process of upgrading from version 0.27.5 to 1.2.1 I’ve decided to take another look at Yarn and what makes it different from npm.

After building my UI on Linux, I popped onto Windows and realized that in Chrome the interface had become larger, as if I was zoomed in.

It was the same company. It was a different company. It was a familiar place. It was a new place. Nothing had changed. Everything had changed.