Why so many issues for such as simple plugin?

[Nenad Novaković]

Everything below tested in Nuxt 3.

• Example to define it as a plugin leads to hydration missmatch, even when <Toaster /> is used within <ClientOnly> component
• Using headless option toast.custom(VSonner) does not really do anything
• Cannot customize CSS Properties (variables) without using !important
• Passing unstyled to toastOptions does not do anything

Also, if someone managed to make headless option work, does it receive props or something to get idea if it's warning/error/success/info, what's the title/description, etc? Otherwise, from the docs, headless options seems more like static toast, rather than headless (fully customizable)

Please let me know how to make it work properly?

[Robert Soriano]

unstyled prop is there but is actually not implemented internally

[Behon Baker]

@dvlden You can look how I customized this package a little in my lib: https://ui-thing.behonbaker.com/components/vuesonner

The implementation can be found here: https://github.com/BayBreezy/ui-thing/blob/main/components/Ui/VueSonner.client.vue

Hopefully this answers a few of your questions.

[rust-Floppy]

<< Created a new issue, thanks for the quick reply to @warflash ! >>

[Nils Wiesinger]

@idk-floppy Would be nice if you could open a seperate issue and put a reproduction of your code/issue there.
pnpm is not a typo in the readme fyi - it's a faster alternative to npm

[rust-Floppy]

@idk-floppy Would be nice if you could open a seperate issue and put a reproduction of your code/issue there. pnpm is not a typo in the readme fyi - it's a faster alternative to npm

Okay, thank you for the quick answer!