2
yehaaw
3y

Has anyone used Storybook for Angular components (or other framework)? Would be interested to hear advantages and disadvantages.

Thanks!

Comments
  • 1
    I found it nice if you really want to build a design system and component library for a big project.
    But the dependency is quite convoluted and it will slow your development down significantly. You must decide if it is what you want. What it does it does well but I wouldnt use it if nobody gives a shit about perfect design and isolated component library. It comes with a cost.
  • 0
    I used it with React. It’s nice if you’re used to building small components where you want to focus on UI. You can develop the component independently and then integrate it wherever you need to use it once it’s ready. It’s also nice when you need to test a component’s behavior based on the properties (or input) it’s getting. As Crismon said though, there’s a maintenance cost. As there would be for any other type of testing tool. If the component evolves, it’s Storybook needs to evolve too.
Add Comment