-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: vue-component-meta docgen HMR not working #27514
Comments
I'm also seeing this issue on 8.1.10. |
I'm also seeing this issue on 8.2.6. |
HMR doesn't work for my either when using Storybook 8.2.6 and the vue-component-meta plugin (also mentioned in #28817) |
The interesting thing is: in a Storybook sandbox project for Vue, the HMR works as epexcted and the args table gets updated as well (when you refresh the browser with F5) |
I tested the examples in the Storybook sandbox repo using Stackblitz, and I noticed that the docgen option is not set to "vue-component-meta" in .storybook/main.ts, which means I'm still using the default value, "vue-docgen-api". That's why HMR works as expected. However, if I set the docgen option to "vue-component-meta", HMR breaks again. As for the second question, why the args table in the sandbox project looks more like it's using "vue-component-meta" than "vue-docgen-api", it's because all the .vue and .stories.ts example files are well-defined. If you follow the examples, you'll get a nicely formatted args table with props, events, and other sections as well. |
cc @larsrickert |
Describe the bug
Hi,
i've noticed that when using the new "vue-component-meta" docgen, the story is not updated at all in dev-mode.
Only a forced dev-server restart will show the updated content of the story
It looks like the HMR is working, but it does not update the args table properly.
This issue has been briefly mentionned here as well #26465
Am i missing something ?
Thanks !
Reproduction link
https://codesandbox.io/p/devbox/vue3-storybook-vue-component-meta-hmr-r6n2ns
Reproduction steps
intent
props comment)System
Additional context
No response
The text was updated successfully, but these errors were encountered: