so does this mean SvelteKit is able to preload components/pages with await expressions? if so, does it respect the current tap/hover preload configuration of anchor tags that we’ve already had?
this does feel like something that 1) would be quite common practice, if more people understood streaming SSR, and 2) arguably should be default behavior in terms of both SEO and initial load time concerns, so I would expect the framework to take care of this, which is also SvelteKit’s core theme
while you’re on the topic of streaming for remote functions, would it be possible to sneak in metadata streaming (for <svelte:head>) as well? that is the only thing I miss from Next.js, where they let you *not* block page render for SEO-related data fetching, but have it be fully awaited for bots.
