Proper way to check navigating in svelte 5

[gterras]

Hi,

I svelte 4 I used to do {#if browser && $navigating}, the $navigating store was undefined when no navigation was active.

In svelte 5 it seems that the navigating state is always defined. The docs say Values are null when no navigation is occurring, so what should I test for to be safe ? I suppose from and to at least ? Is there a case where from is not null but to is ?

This probably could be mentioned in the migration guide.

[brunnerh]

I would check the type property. from and to can potentially be null when a navigation is happening, type cannot (at least according to the type definitions).

The rune based state objects are an additive feature of SvelteKit, so they are separate from the Svelte 4 to 5 migration, though they do require runes. Not sure whether this should be tacked onto the existing guide or whether a separate document in the SvelteKit docs would be a good idea. For most of these store migrations the path should be straightforward.

[gterras]

Thanks for this, it took me some time to figure out what was happening.