Jacob Janisz

We use CSS vars approach in component library and ideally we would like it to be documented the same way as props, events, slots and models, maybe something like this...

I stumbled upon https://stackoverflow.com/questions/72003493/how-to-use-jsdoc-to-document-a-vue-component-with-script-setup to see how to add component description when you use `` and I can confirm adding another `` tag with description alongside `` is not working.

I use them both and have no issues with latest storybook vue 3 vite config. Maybe try adding separate `vite.config.ts` inside `.storybook` folder instead of using `viteFinal` property? It loads...

> package version > vue 3.3.4 > vite 4.3.4 > vite-plugin-vue-nested-sfc 0.1.2 > vite 4.3.4 > astrojs/vue 2.2.0 > I was trying to migrate my app to using this plugin...

@tobiasdiez any update on this? I love using `.vue` files instead of `CSF` but I've had to ditch it as lack of args customization is a show stopper for me...

Duplicate of #16372 ?

Temporary TS workaround: declaring it globally via `.d.ts` file: ```ts // defineMeta.d.ts import type { Meta } from '@storybook/vue3' declare global { /** * Vue compiler macro for defining metadata...

I'm not 100% sure on whether the issue lies in Histoire or Agnostic UI so I created an issue on Histoire as well https://github.com/histoire-dev/histoire/issues/542

I managed to find a workaround to use the 'raw' components from source. Looks like the issue lies in built script for ES6 modules. ```vue import { Button } from...

> Reverting commit [bcf68df](https://github.com/nuxt-modules/storybook/commit/bcf68dff2ca3353733c4dc60f479f44b8c0cd15d) stops the error, but images are broken, maybe it's just a matter of adding `staticDirs` to `.storybook/main.ts`. > > Ok, so temporary workaround for anyone struggling...