Share your feedback...
Add ability to run multiple frameworks in 1 storybook
Some users are migrating from one framework to another, or just have some components in different frameworks for some reason. Storybook should support showing components of any framework in 1 storybook, setting up 2 different storybooks for them really breaks the idea of having a centralised place for all your components.
Write a live code edit addon
Write a https://react-live.kitten.sh/ sequel addon but for any storybook framework.
Storybook can be quite slow on large codebases with many components. We want to make improvements to our bundling mechanism/config so it's faster. Long term goal is to have each component-story have it's own html-file output, so the bundle will split into smaller ones.
Will there be support for flutter-development?
I did not found any information about supporting other languages and frameworks in the future. I am hardly interested in using Storybook with flutter. (I know there is something like an addponproject but that does not fit my needs) Thx for any information regarding that topic. Have a nice day!
Current CLI is basically a single black box magic command that installs storybook (if framework detected) and that's it. Having a richer CLI so that users can have more control over their Storybook in one single place would be awesome. Original issue and ideas at: https://github.com/storybooks/storybook/issues/1108
Ability to use Nunjucks, Handlebars, etc., in Storybook
Some projects use templating engines, such as Nunjucks, Handlebars and others, to create UI components. And it will be great to add that feature in Storybook too.
useNavigate() from React 6
useNavigate() from React 6 is breaking storybook. Any plans to update storybook to version 6?
Storyshots continues feedback during run
Also see: https://github.com/storybooks/storybook/issues/3590 The way storyshots currently works prevents it from showing feedback during runs. Only after every story has been run, is there any feedback. This is disturbing especially for large storybooks, as the process seems to hang, and gives the impression is broken. It would be much nicer is all stories are run individually. This has a couple of other improvements as well: The stories can be sharded over multiple CPU's, individual stories can be re-run and failures are detected faster. The idea is to overhaul storyshots to not wrap ALL stories, but instead run story-files directly in jest, and provide a storybook facade for it's api's. This would remove a lot of complexity for us as well, as most options can be deprecated.