I'm using StoryBook to rejuvenate the React App
by Chris HartwigWhen you want to work on a 3 years old React App, you realize a lot has changed! Everything has become obsolete, and a lot of APIs have changed.
I've decided to upgrade everything: I don't just want the app to become a business, I want to build upon it in the future.
Also, I'll deploy it as I deploy apps now, with Docker.
There's still a lot of work to do...
-
1
I use Vue and I think it has StoryBook available too.
I've heard a lot about it - and I definitely want to give it a shot. How is the StoryBook integration going? In the end is it a helpful tool?
-
1
Integrating Storybook is a little like integrating unit testing: you add stories to your project, that are using the StoryBook JS module, and you can run a local StoryBook server to see the result and iterate.
I find it very useful because it lets you focus on your components and nothing else.
It's like unit testing (StoryBook) vs. integration testing (running the app in dev mode).
In my case, it helps me because the app doesn't even compile anymore after upgrading dependencies... so I must focus on one component at a time to update everything!
Definitely worth a try, and easy to learn too!
-
