SSR without pending boundary causes reactivity loss

[dummdidumm]

Describe the bug

Async SSR without a pending boundary causes reactivity loss somehow

Reproduction

Wasn't able to wittle it down more yet, but this repro shows the issue: the remote function is SSR'd, stuff hydrates, but updates are not recognized anymore (remote functions themselves work correctly as seen in the network tab or when you disable SSR)

Logs

System Info

irrelevant

Severity

blocking an upgrade

[timootten]

Here’s the state of the repository where the bug is present:
https://github.com/timootten/SvelteKit-Remotefunctions/tree/52326a198c20df09aabcbabd06319ccbf15af644

I’ll be pushing other commits to this repo that aren’t related to this bug.

[hyunbinseo]

I was experiencing the exact same issue today.

Might be a duplicate of #16905

1. hydration_mismatch is logged in the console
2. Wrapping with <svelte:boundary> fixes the issue