You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would love to see easy support for interacting with different <slot/>s inside components
I'd also like this feature, including a defaultSlots in the extendCompodiumMeta .
For example, my Button only accepts a default slot for text, so I want to be able to view my button with 'Hello World!' in the default slot when I open Compodium.
Thanks for the great work so far @romhml, love the multiple variants display!
It should be possible to do something with extendCompodiumMeta to pass string values for slots, but it'll be hard to support actual HTML / Vue template with it. I'll think about it!
Can your implementation of vue meta component render the JSDocs for each prop in markdown?
Asking specifically for the links. When I use the link syntax --> here, it does not present a clickable link. It renders the text as is
This is what I have for the JSDoc over the prop
/** * The icon to display inside the component. * * Can be a string from the [Icônes library](https://icones.js.org/) or a Vue component (VNode). * * @see [Icônes library](https://icones.js.org/) */
icon: VNode|string;
Thanks for the amazing work on compodium @romhml ! do you have any rough timeline in mind for the “Build and publish your playground”? Being able to share the playground with non-developers on the team would be a huge win for us.
One small suggestion as well, it would be great if components could be grouped based on the Nuxt components directory structure instead of all living in a single flat list, that would really help with larger projects.
Thanks! I'm struggling a bit to find time to focus on the project right now, so I can't really say when I'll be able to. My first goal is to wrap up the vitest integration and move on to the publish feature.
Hey, just wondering @romhml, how active in development is this? I was previously using histoire but I am ditching it due to lack of nuxt support and simply any activity as there are tons of issues/prs opened and unanswered and I fear compodium could go to that route.
I am merely concerned, and wondering if I should just use storybook or this.
PS: Having a discord for the project would be nice potentially.
Hey @xMrAfonso ! Like I said in the comment above I haven't been very active lately. If you are looking for stability you should definitely go with storybook.
I'll look into opening a discord server at some point, in the meantime, feel free to reach out to me directly on discord if you have any questions.
Activity
brenodanyel commentedon Mar 3, 2025
Waiting for plain vue support! Great work!
Norbiros commentedon Apr 17, 2025
I would love to see easy support for interacting with different
<slot/>s inside componentsromhml commentedon Apr 18, 2025
@Norbiros do you mean something to specify component slots similar to the props tab?
Norbiros commentedon Apr 19, 2025
Probably yeah
RensBoeser commentedon Apr 23, 2025
I'd also like this feature, including a
defaultSlotsin theextendCompodiumMeta.For example, my Button only accepts a default slot for text, so I want to be able to view my button with 'Hello World!' in the default slot when I open Compodium.
Thanks for the great work so far @romhml, love the multiple variants display!
romhml commentedon Apr 24, 2025
@RensBoeser the current way of achieving this is to add an example for your button:
compodium/examples/MyButtonExample.vueIt should be possible to do something with
extendCompodiumMetato pass string values for slots, but it'll be hard to support actual HTML / Vue template with it. I'll think about it!Norbiros commentedon May 20, 2025
Another idea is to add zoom in/out controls, allowing users to inspect smaller components more easily without scaling the entire UI...
BayBreezy commentedon Sep 29, 2025
Can your implementation of vue meta component render the JSDocs for each prop in markdown?
Asking specifically for the links. When I use the link syntax --> here, it does not present a clickable link. It renders the text as is
This is what I have for the JSDoc over the prop
Ala-Hanoun commentedon Feb 9, 2026
Thanks for the amazing work on compodium @romhml ! do you have any rough timeline in mind for the “Build and publish your playground”? Being able to share the playground with non-developers on the team would be a huge win for us.
One small suggestion as well, it would be great if components could be grouped based on the Nuxt components directory structure instead of all living in a single flat list, that would really help with larger projects.
Thanks again for the awesome work!
romhml commentedon Feb 9, 2026
Thanks! I'm struggling a bit to find time to focus on the project right now, so I can't really say when I'll be able to. My first goal is to wrap up the vitest integration and move on to the publish feature.
xMrAfonso commentedon Mar 18, 2026
Hey, just wondering @romhml, how active in development is this? I was previously using histoire but I am ditching it due to lack of nuxt support and simply any activity as there are tons of issues/prs opened and unanswered and I fear compodium could go to that route.
I am merely concerned, and wondering if I should just use storybook or this.
PS: Having a discord for the project would be nice potentially.
romhml commentedon Mar 23, 2026
Hey @xMrAfonso ! Like I said in the comment above I haven't been very active lately. If you are looking for stability you should definitely go with storybook.
I'll look into opening a discord server at some point, in the meantime, feel free to reach out to me directly on discord if you have any questions.