reactjs / react-gradual-upgrade-demo Goto Github PK

Sorry for my ignorance, but I never saw this approach before.

Why is this needed? Should people who do not use two react versions of the app be aware of this approach? Will something like that work with typescript?

p.s. just a note on presentation, it would be cool to see how you take this demo working with react 16 and convert it to gradual upgrade demo, instead of the whole app being in one "initial commit" where it's hard to reason about which parts are relevant to what.

Hello!

I’ve read the README and it notes that this demo essentially re-creates the functionality of React.lazy but I can’t see any explanation as to why that is the case.

So...why is it so?

Here's the quote from the blog post https://reactjs.org/blog/2020/08/10/react-v17-rc.html

Thanks to this change, it is now safer to embed a React tree managed by one version inside a tree managed by a different React version. Note that for this to work, both of the versions would need to be 17 or higher, which is why upgrading to React 17 is important.

Note that for this to work, both of the versions would need to be 17 or higher

But this repository uses React 16 inside React 17, could it possibly create bugs with events?

The application i work is a legacy one with react version 16.2 and typescript 3.3.1. For modern, planning to use the recent version of react 17.0.2. Can we have multiple version of tsconfig and generate builds?

sorry, I can't understand the solution in the docs, please could you explain it and tell me how to solve it，thanks ~~