Daniel Husar

Progressively upgrading React in your app

1 minute read

Upgrading React means upgrading one of the most critical dependencies of your app.

Even if all your unit and integration tests pass, you will probably not feel comfortable shipping major upgrade of React to all customers at once.

If you are using Webpack and Yarn, you can create two bundles of your app with different React version and test upgraded React only for the small percentage of your customers.

If your package.json looks like this:


You can install next React version together with your current with Yarn aliases:


Now you can use import React from 'react-16' to import the upgraded version of React. You can automate it with Webpack resolve alias.

A simplified version of Webpack config might look like:


Webpack supports both single config export or exporting an array of configs. Using resolve alias for another entry, we can create two bundles of the same app with different React version:


The config above will create a new main_react_16 bundle with React 16 in addition to our original main bundle, with both bundles being in sync every time you deploy a new version of your app.

If you are using error tracking software like Sentry, you can also add a tag with React version to each event:

While React is my framework of choice, you could use the same approach for Ember, Angular, Vue or any NPM library.