page data store now runes state

[shiftlabs1]

The stores expected in sveltekit-flash-message as parameters are writable stores and page store is now a runes store. this will need updating.

[hgoona]

The stores expected in sveltekit-flash-message as parameters are writable stores and page store is now a runes store. this will need updating.

is there a way to get past this?

[alexweber]

@hgoona It actually still works, you just gotta import the old page store and ignore the deprecation warnings:

<script lang="ts">
// Using both the new page from app state for other things and old one for flash messages.
import { page } from '$app/state';
import { page as pageStore } from '$app/stores';

const flash = getFlash(pageStore);
</script>

{#if $flash}
   <div>{$flash.message}</div>
{/if}

Caveat: if you are setting flash messages on the server before a redirect you will get taken to an error page for a split second before the redirect kicks in. I assume this is due to the Svelte 4 to 5 migration.

It's a little annoying but I'm ok with it for now...

[ciscoheat]

If there's a way to detect which one of the stores are used at runtime, I could add a compatibility fix.

[ciscoheat]

With 2.4.5 it should now be possible to use $app/state as well as the old $app/stores, check it out and see if it works.

[bagaskarawg]

@ciscoheat Working great with Svelte 5.