kevin olson
kevin olson
can you make the change to the actual source as well? not just the build file?
@abotalebie there is nothing particular other than overriding the CSS classes yourself - you can see the defaults here https://github.com/fumeapp/tailvue/blob/main/src/toast.ts#L6-L14
well one idea: i set an `id` to the container element all of the toasts fire from [here](https://github.com/fumeapp/tailvue/blob/main/src/toast.ts#L24) - maybe you can do something like this: ```css #toasts { @apply...
Glad to hear this works - ill update the readme and think about a way to add official support when i get time - otherwise feel free to submit a...
@danielroe does this mean it's possible if i define them elsewhere?
reading into NuxtPage @danielroe and @exreplay 's example.. i'm still not really following on how I can use `NuxtPage` @exreplay are you able to show off an example using pages/layouts?
@danielroe is this option you suggested in rc.12 ? is there any new workarounds or methodology to help make this possible?
oooh this looks new! https://v3.nuxtjs.org/getting-started/transitions#dynamic-transitions
with the updated docs i am now trying out: ```ts definePageMeta({ pageTransition: { name: 'page-left-to-right', mode: 'out-in' }, middleware (to, from) { const toInt = (name) => parseInt(name.toString().replace('step-', '')) to.meta.pageTransition.name...
sure @Atinux ! funny i keep coming back to this for other projects as the example - simpler version might be useful on the docs