useState initializer called multiple times with suspense about react-ssr-prepass HOT 5 CLOSED

Nice catch! I’m pretty sure though that React itself gives no guarantees these will only be called once across suspends. See for example this issue.

from react-ssr-prepass.

Thanks @Ephem ! While that behavior is unfortunate, it sounds like it's the 'correct' behavior at the moment.

from react-ssr-prepass.

Yeah, it confused me at first too. 😀 It’s equally correct to memoize across suspends of course, so it’s definitely possible to implement this as an optimization!

from react-ssr-prepass.

This'd be nice, as it would allow executing and caching suspense promises on mount

from react-ssr-prepass.

@achung89 You should avoid caching suspense promises or other “global loading state” in a single component’s state. This may cause subtle bugs that are then hard to iron out. Chances are you may want to have a shared cache across context if you’re doing this, but of course, libraries exist to make it easier to handle fetching logic, although some don’t play nicely with suspense.

If you really need state across suspenses in react-ssr-prepass then maybe try using a ref. It’s worth noting though that React itself doesn’t usually preserve any state across suspense.

from react-ssr-prepass.