Filip Joelsson
Filip Joelsson
I tried to be creative and solve this by parsing the sanitized HTML and supply it as childNodes in `getSSRProps`. That didn't work either :-( (I might add that I...
There is a PR for a temporary fix in this package here: https://github.com/nuxt-modules/storybook/pull/447 I have also submitted a fix to the get-port-please project here: https://github.com/unjs/get-port-please/pull/72 (If you want them to...
Is that by a Storybook maintainer? Good to know. I've tried that one too, and it is buggier than this project, but if it is maintained it may be worth...
I'd like to add my thanks. I also use the canary in our (smaller) setup. Works nicely with our graphql calls!
Here's the bug in nuxt-gtm that this would solve (at least in my use-case): https://github.com/zadigetvoltaire/nuxt-gtm/issues/14
> Is it possible to add a test for this? So we can prevent regression? I'll see if I can come up with a way to test it. What triggered...
I agree. There's a blog post about this use-case here: https://www.liip.ch/en/blog/nuxt3-node-debugging (Would a patch be welcome?)
I also ran into this. I solved it by wrapping things in `useNuxtApp().runWithContext(async () => { /* my code here */ })` I think this is more like a limitation...
We have a similar problem. In addition, it seems Vite is removing the gtm object entirely when minifying - since it isn't defined.
It seems Vite does something unexpected when minifying code. (For me, it copied the useGtm function instead of importing it, but useGtm was relying on a locally scoped variable.) This...