Closed literalpie closed 1 year ago
The cause of this is that QwikCity and Storybook both try to do things to MDX.
qwikCity({ mdx: { mdxExtensions: [], mdExtensions: [] } })
), but that's not great because we don't want to lose other settings that the user might be passing into the plugin.as a stop-gap, I think I'll go with the first approach. I'd rather have docs working even if it means overwriting config.
Even once I got docs working with that workaround, I don't understand storybook docs. I need to learn more about how it's supposed to work.
One important thing to know is that storybook doesn't even try to support other frameworks in the stories mdx files. The only way to run Qwik components in story mdx files will be through stories (or making our own React wrappers for qwik components.)
See the linked commit. I was able to find a solution a little more fine-grained than the comment above suggests. I only take out the transform
part of the Vite plugin, which is where only md/mdx transformation stuff is. I think this is a pretty good solution without compromise (user-defined non-mdx config still happens)
I get this error if MDX is included in the storybook configuration (which it is by default)