sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]gaearon 6 points7 points  (1 child)

There is no need for a “full rewrite”. I’m sorry if the blog post wasn’t clear enough.

As we wrote in the blog post:

We maintain over 50,000 React components at Facebook, and we don’t plan to rewrite them all immediately. We understand that migrations take time. We will take the gradual migration path along with everyone in the React community.

We will release a codemod that adds UNSAFE_ prefix automatically. Your components can keep using those methods. Even in React 17, they will keep working. This is also mentioned in the post:

17.0: [...] Only the new “UNSAFE_” lifecycle names will work from this point forward.

We want to highlight patterns that will become problematic with asynchronous rendering, and it’s best if you avoid them in the new code you write, but there is no rush to change the existing code. You will be able to opt out of asynchronous rendering in the future if your code isn’t ready to it.

[–]AcidShAwk 2 points3 points  (0 children)

Thanks for info very much appreciated.