I've seen a few React polyfill projects pop up recently that experiment with upcoming APIs. It's great to see people excited about the changes we're working on
but I think we should all move carefully to avoid causing any unnecessary fragmentation in the community.
Within Facebook there are presumably lots of components written using the old lifecycle methods. Are there applications and libraries that will not be updated? I wonder how you manage large-scale upgrades internally? Do you continue to support old versions of React?
-
-
Facebook is always using the latest version of React. (Right now it's using the alpha version.) The volume of React components we have (~50,000) means that upgrade paths need to be gradual and even codemodable whenever possible.
-
I figured this was the case, and I'm interested in how this works in practice. Would love to see a blog post on how this is achieved. Can you codemod between lifecycle methods or do you write lint rules to find them and then teams get tasked with upgrading them?
- 3 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.