I was thinking the same re: Storybook. Though I was trying to figure out what benefit Cosmos may have over storybook?
I'm using Storybook with React-Native, and it does feel like I'm developing web components, and then trying to use them in an app later, but that's my only real complaint with Storybook.
Ive strung up spas within storybook so I have the component and the page its going into. Essentially you import the <App> and provide a store. It helps single responsibility principalize your code, and you are always focused on having well define components for your storybook library/dictionary.
Do you have any examples you can share where you've customized Storybook in this manner?
If I understand correctly, as opposed to loading your components in isolation in Storybook, you're providing them with a context similar to the actual app they're going to exist in?
Not OP, but i suppose you can use custom decorator to wrap components and globalTypes for some customization, like theme selector
https://storybook.js.org/docs/react/essentials/toolbars-and-...
This sounds like a good use case for Playroom too
I definitely see a future where the IDE has much more awareness of your development environment, this is a step in that direction at least for React.
Game developers get a lot of these benefits from their IDE typically having more tools than webdevs with a text editor. Hoping to see more of this in the future!