Artem Manchenkov
Artem Manchenkov
Same here 👍 ```vue // ... const uniqueIdentifier = useId(); // ... ``` This workaround helped, ofc as temp solution ```typescript const uniqueIdentifier = useId().replace(':', '_'); ```
Hey @j-jalving, I agree, but the main idea of this module was to provide an easy way to set a cookie-based authentication for SPA apps. If you need token-based solutions,...
@yuzu-qroulland yep, that works! thanks 👍
just fyi, since I upgraded to Nuxt 3.8 it works even with default config like ```typescript image: { quality: 80, format: ['avif'], ipx: { maxAge: 60 * 60 * 24...
I was also struggling with this issue, but it was in a slightly different environment. I have a plugin that provides a custom `$fetch` client and I want to trigger...
I also noticed weird behavior, maybe it will help, for example, I use Nuxt UI, and in `.nuxt/components.d.ts` it resolves only `client` components: ``` // doesn't work 'UModal': typeof import("../node_modules/@nuxt/ui/dist/runtime/components/overlays/Modal.vue")['default']...
Yep, with 2.0.14 it seems fixed
let me leave it here in case someone also wants to find an example of sanctum + nuxt with SSR support 😄 Article about [implementing SSR on Medium](https://medium.com/@manchenkoff/laravel-10-and-nuxt-3-setup-ssr-with-authentication-from-scratch-497ab1a3fc56) And [source...
@yoyossef also suggested adding `ref` as a field of schema (see #48)
Hey @emelymw, nope, currently there is no workaround since the initial parsing is out of the control of this package.