# React v17.0

DevFeed: [React v17.0](<https://devfeed.tech/articles/react-v17-0-22342.md>)

Original publisher: [Read original article](<https://reactjs.org/blog/2020/10/20/react-v17.html>)

Published: 2020-10-20T00:00:00Z

Content type: release

Language: en

Sources: [React](<https://devfeed.tech/sources/react.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [upgrade](<https://devfeed.tech/topics/upgrade.md>), [App](<https://devfeed.tech/topics/app.md>), [dialog](<https://devfeed.tech/topics/dialog.md>)

Tags: [developer](<https://devfeed.tech/tags/developer.md>), [react](<https://devfeed.tech/tags/react.md>), [release](<https://devfeed.tech/tags/release.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

## AI overview

React 17 is released as a stepping-stone update focused on making React upgrades easier. It enables safer coexistence of different React versions and supports gradual upgrades, while adding no new developer-facing features.

## Source excerpt

This blog site has been archived. Go to react.dev/blog to see the recent posts. Today, we are releasing React 17! We've written at length about the role of the React 17 release and the changes it contains in the React 17 RC blog post. This post is a brief summary of it, so if you've already read the RC post, you can skip this one. No New Features The React 17 release is unusual because it doesn't add any new developer-facing features. Instead, this release is primarily focused on making it easier to upgrade React itself. In particular, React 17 is a "stepping stone" release that makes it safer to embed a tree managed by one version of React inside a tree managed by a different version of React. It also makes it easier to embed React into apps built with other technologies. Gradual Upgrades React 17 enables gradual React upgrades. When you upgrade from React 15 to 16 (or, this time, from React 16 to 17), you would usually upgrade your whole app at once. This works well for many apps. But it can get increasingly challenging if the codebase was written more than a few years ago and isn't actively maintained. And while it's possible to use two versions of React on the page, until React 17 this has been fragile and caused problems with events. We're fixing many of those problems with React 17. This means that when React 18 and the next future versions come out, you will now have more options. The first option will be to upgrade your whole app at once, like you might have done before. But you will also have an option to upgrade your app piece by piece. For example, you might decide to migrate most of your app to React 18, but keep some lazy-loaded dialog or a subroute on React 17. This doesn't mean you have to do gradual upgrades. For most apps, upgrading all at once is still the best solution. Loading two versions of React -- even if one of them is loaded lazily on demand -- is still not ideal. However, for larger apps that aren't actively maintained, this option makes sen