My experience with React 16

  • If you have a React 15.5 app which doesn’t use deprecated features and doesn’t throw errors, then React 16 just works!
  • One of my favorite things about React is that it gives me access to a great library of open-source components.
  • And thanks to the stability of React’s API, I haven’t needed to upgrade many of these components… until now.
  • In previous versions of React, throwing exceptions within event handlers would have unpredictable results.
  • While React’s API hasn’t changed much, it has an entirely new engine under the hood called React Fiber.

Now I don’t want to waste your time with another “What is React 16?”; the official blog is already very informative. But what I can give you is the story of my experience this week, when I upgraded a large project to React 16.

If you haven’t already heard, the big news over the past fortnight is that React 16 was released.

Now I don’t want to waste your time with another “What is React 16?”; the official blog is already very informative. But what I can give you is the story of my experience this week, when I upgraded a large project to React 16.

If you have a React 15.5 app which doesn’t use deprecated features and doesn’t throw errors, then React 16 just works!

Of course, “it just works” doesn’t make for a very interesting story. So lucky for you, it didn’t just work for me.

One of my favorite things about React is that it gives me access to a great library of open-source components. And thanks to the stability of React’s API, I haven’t needed to upgrade many of these components… until now.

React 16 no longer exports , , or . These were deprecated in React 15.5, but now they don’t work at all.

You can still use these by adding the appropriate package to your project. Unluckily for me, my app depended on some unmaintained packages that still accessed , so I took the opportunity to find alternatives. This was the only really painful part of the upgrade.

In previous versions of…

My experience with React 16