Post

Hear me out! @vite.dev plugin `vite-plugin-svelte-docgen` What could be potentially more desired by you, @svelte.dev developer? 1. Transforming compiled output of `*.svelte` file to add `__docgen` key with data 2. Creating virtual modules `virtual:./Button.docgen.js`?

I think option 2 makes a lot more sense. It's safer, it doesn't depend on Svelte's internal compilation that can change at any time because it's not a public API.

You could make it importable from '~svelte-docgen:some/file/path.svelte', a bit like unplugin-icons work. github.com/unplugin/unp...

Hmm. That's worth consideration too! CC @ciscorn.bsky.social I have concern that both formats doesn't exactly align with Vite's Virtual Modules Convention: vite.dev/guide/api-pl... I think it should be: `virtual:svelte-docgen:/path/to/component.svelte`? And the virtual module is pure JS. 🤔