Gradual Adoption Strategy of React 18

Michael Chan
InstructorMichael Chan
Share this video with your friends

Social Share Links

Send Tweet
Published 2 years ago
Updated 2 years ago

In this lesson Michael Chan explains the design of React 18's gradual adoption strategy, what it means for your apps, and further in the course you'll see how to start testing with prerelease React 18 today.

Instructor: [0:00] Hey, friends. Welcome to this course on migrating client-side apps to React 18 Beta. React 18 is an extremely exciting release. It's something that we've been waiting for for a long time.

[0:13] If you think about it, it boils down to, we want to introduce a bunch of groundbreaking features but also don't touch anything. We want everything to work the way that it did before. React calls this their gradual adoption strategy. What does that mean?

[0:29] In the short term, it means that, despite React 18 shipping with a host of new features, using the same APIs in the same ways as you do with React 17 will yield the exact same results as you had in React 17.

[0:43] However, there's a bunch of performance improvements that can be gained by changing our root API and updating the way that we interact with state updates. That's what this course focuses on, is going through all of the changes that are a result of changing that root API and places in your app that you might need to update to get the most performance benefit from these changes.

[1:07] Once you've made those changes, your app is in a stable place to take advantage of all of the new and upcoming features in React 18. Without further ado, let's dive in.

egghead
egghead
~ 13 minutes ago

Member comments are a way for members to communicate, interact, and ask questions about a lesson.

The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io

Be on-Topic

Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.

Avoid meta-discussion

  • This was great!
  • This was horrible!
  • I didn't like this because it didn't match my skill level.
  • +1 It will likely be deleted as spam.

Code Problems?

Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context

Details and Context

Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!

Markdown supported.
Become a member to join the discussionEnroll Today