test(rsc): add SSR thenable workaround in examples

[hi-ogawa]

Description

• Related Bug: React.use inside React.lazy-ed component returns other React.use value on SSR facebook/react#33937

TODO

• test

[pawelblaszczyk5]

Oh, so that's what I was experiencing lately 😄 I was surprised by some weird behavior where promise resolved to a different value for a moment. However, it seems for me that this fix doesn't solve the issue? https://github.com/pawelblaszczyk5/vite-rsc-experiments/tree/main/apps/error-boundary

Do you have any ideas?

Also, surprised a bit by difference between experimental/canary - it's fixed in React experimental channel for me, but broken in canary.

[hi-ogawa]

There is async in the wrapper and this doesn't serve as a workaround since we are trying to eliminate React's internal thenable state (which kicks in either use or async/await component) https://github.com/pawelblaszczyk5/vite-rsc-experiments/blob/0112085c32c87674a1949e42d662f3e94b499392/apps/error-boundary/src/framework/entry.ssr.tsx#L11

This should be simply:

const SsrUseWorkaround = (props: React.PropsWithChildren) => props.children;

The original React issue facebook/react#33937 reproduces on all channels. Though there might be some variance on how it reproduces depending on component tree and maybe some scheduling, I think the underlying issue is on React.