[Flight] Fix Client components losing state on refetches

[gaearon]

Fixes test in #20318.

I bet there's some better fix. But the problem is that this trick causes creation of lazy wrappers on the client, which would be different between refetches. Maybe they should be cached globally? For now, removing this seems to work.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit b64032c:

Sandbox	Source
React	Configuration

[sizebot]

No significant bundle size changes to report.

Size changes (experimental)

Generated by 🚫 dangerJS against b64032c

[sizebot]

No significant bundle size changes to report.

Size changes (stable)

Generated by 🚫 dangerJS against b64032c

[sebmarkbage]

These are important. I’m surprised we don’t have tests.

Lazy elements exists in core exactly for the reason to enable them to reconcile so I’m sure this is just some oversight somewhere.

[sebmarkbage]

I think I meant to change the lazy type semantics to reconcile but I ended up doing it only for the element type.

We should do it for the element type too in childfiber.

There’s no reason the existing usage of lazy shouldn’t reconcile when the same component is imported using two different lazy wrappers.

[sebmarkbage]

This is the path that got lost. https://github.com/facebook/react/pull/18362/files#r532953847