Chris-Robin Ennen

Same issue here! Thanks for the tip, I explicitly include files, so I only had to change the order in `tsconfig.json` so that the AutoImport typings are included after the...

Actually, nevermind. I misread and thought the first line with `this page is: ` is incomplete. However, I **do** have this exact problem with my integration and I have no...

Anything I could do to help? Still not working for me, which is a bummer. I can't deploy my app on vercel like this.

@brillout I'll take a look at Pinia, Vuex is sorta deprecated nowadays.

> > Seeing https://www.reddit.com/r/vuejs/comments/1dsucor/vike_june_releases/ it seems that Vike's flexibility doesn't resonate with most users. For those a direct comparison with Nuxt is crucial, as it's probably the only way to...

Just to give my two cents here - is this really something to implement ourselves? I've been using https://unhead.unjs.io for some time now and really like it, so I wouldn't...

> An easy workaround would be that we write the `d.ts` ourselves, instead of using the generated one. Could you elaborate? My thinking was doing something along these lines `ClientOnly.vue`...

Working on it. See my PR #88 I'm guessing ids for the teleport roots should be enough. Let me know if this would work for you, then I'll release it...

You're right, I never even thought about having nested teleport targets. Also, we could support teleports to `body` without any user config. However, wouldn't supporting a nested data structure be...

Yes, I was thinking of turning this into `['teleports-container', ['teleport-modals', 'teleports-notifications-container', ['teleport-notifications-top']]]` Looking at it now though, this might get a little confusing. Edit - I just saw that one...