As Michael Shilman said, in our case we have storybook as a separate tab inside our demo app:
Regarding the workflow of splitting out the Storybook I don’t have one recommended way to do it. I had described the process a little bit here:
Sorry for not explaining how to do it in the post itself, it would have increased the length of it by quite a lot. I…
In our own case we have a complicated build process where all our code is registered as modules so we can say in the config to not include Storybook at all.
I don’t recommend to ship storybook code in the app. It doesn’t add a lot of overhead but still that code increases bundle size which slows down the app startup itself.
If you have any questions feel free to ask :)