SSR Support

[iluvsoup]

Currently this package doesn't seem to support SSR because of it's use of document

Not that important but it would be nice to have

I'm using SvelteKit

[iluvsoup]

This error appears after refreshing whilst a toast is active (or in my case, a form submission)

[zerodevx]

Thanks for the bug report. This is introduced in v0.8 - FWIW it's supposed to work since document is only used in onMount() and should only run client-side... but I think I know what's wrong. I'll submit a fix soon.

[zerodevx]

@iluvsoup - I published a fix in the @next tag. Could you help test and see if the error shows again? 🙏

You can install with:

$ npm i @zerodevx/svelte-toast@next

[iluvsoup]

Works great other than a visual bug whenever I refresh the page

2022-11-03.21-43-52.mp4

It happens on both chrome and firefox, could it be a svelte quirk?

Thanks for the quick reply by the way

[iluvsoup]

On second thought it might be an issue with my form submission, I'll look in to it

[iluvsoup]

Actually it might be something to do with the stores not clearing on refresh, the toasts don't ever seem to go away

(the outputs of console.log($toasts))

[zerodevx]

Wow, not sure what's going on to be honest. Is the error message gone? Also, could you try installing:

$ npm i @zerodevx/svelte-toast@0.7.2

and let me know if anything changed?

[iluvsoup]

Oh yeah the error message is gone, it's just the store don't seem to clear whenever I refresh which results in the giant wall of toasts

[zerodevx]

Does the wall of toasts still appear with v0.7.2? Trying to isolate.

[iluvsoup]

Yes
Sorry for the late reply, I was sleeping

[zerodevx]

Ah ok, I'm pretty sure we're facing 2 separate issues here. The document is not defined thing happens because while onMount() to guaranteed to only run client-side, it appears onDestroy() may be called during SSR - this will be fixed with #57.

On the other hand, the wall of toasts thing is likely related to your form submission code. If you can post a minimal reproduction, perhaps we can move this to a new issue and try to work it out from there.

For now, I'll publish a patch release which should mark this SSR issue as fixed.