svelte/documentation/docs/98-reference/.generated/server-warnings.md

unresolved_warp

Part of the data added to `Warp` instances was not used during the render, so the response was delayed until it resolved.

The most likely cause of this is creating a value in the script block of your component and then awaiting the result inside a svelte:boundary with a pending snippet:

<script>
	import { Warp } from 'svelte';
	import { getUser } from '$lib/get-user.js';

	const warp = new Warp('my-app');
	const user = warp.getOrInsertComputed('user', getUser);
</script>

<svelte:boundary>
	<h1>{(await user).name}</h1>

	{#snippet pending()}
		<div>Loading...</div>
	{/snippet}
</svelte:boundary>

Consider moving the getOrInsertComputed call inside the boundary so that it's not called on the server.

Note that this can also happen when a value contains multiple promises and some but not all of them have been used.