Hey there, I'm not sure if this is an issue directly caused by the Nuxt Storybook module but it seems to only occur when using it. When I run Storybook either via storybook dev --port 6006 or visiting it on the localhost:6006 server that starts alongside Nuxt, I'm getting an http proxy error on initial page load. Then, if I hover over any of the stories in the navigation that have a slot or a component that uses the self closing syntax (e.g. <slot /> in the template, it'll throw another error.
I've tried commenting out all of my modules in our Nuxt config & rebuilding to rule out third party interference.
It seems something funky is going on with transpiling. I was wondering if this might be an issue anyone has encountered? Is there maybe some additional configuration I need to support self closing tags?
Hey there, I'm not sure if this is an issue directly caused by the Nuxt Storybook module but it seems to only occur when using it. When I run Storybook either via
storybook dev --port 6006
or visiting it on thelocalhost:6006
server that starts alongside Nuxt, I'm getting an http proxy error on initial page load. Then, if I hover over any of the stories in the navigation that have aslot
or acomponent
that uses the self closing syntax (e.g.<slot />
in the template, it'll throw another error.I've tried commenting out all of my modules in our Nuxt config & rebuilding to rule out third party interference.
It seems something funky is going on with transpiling. I was wondering if this might be an issue anyone has encountered? Is there maybe some additional configuration I need to support self closing tags?
Versions: storybook@v8.1.6 nuxt@3.11.2 @nuxtjs/storybook@v8.1.1
First error from initial Storybook load:![image](https://github.com/nuxt-modules/storybook/assets/6605678/ac16c495-5e5e-4973-995d-3556fbdc8b39)
Second error from hovering over a slot/component tag containing component:![image](https://github.com/nuxt-modules/storybook/assets/6605678/51dfb2d0-14b0-48a1-88cb-1e6e564a8fe5)