Creating your own reusable components cross project (Bit.dev Storybook)
I’m rebuilding my site with the T3 stack and I’m going to be having an extremely similar site to it that I also host for premium users. These sites will share a bunch of components so I want to find a way to write my components once and reuse them.
For tooling on this, the two options I’ve found are:
https://bit.dev/
https://storybook.js.org/
Between those, Bit.dev seems like the better option to be as it seems more geared towards reusing your components cross project. It also looks like it lets you write regular typescript code as modules as well which would be helpful.
Had anyone done something similar? If so I’d love to get some feedback on if this is the right approach, if there’s any examples people have of a project setup like this, or any other thoughts on making your work reusable
Thanks!
bit.dev
Bit - Component driven development
Bit is the leading toolchain for component-driven development. Forget monolithic apps and distribute to component-driven software. Build like the world’s best teams.
Storybook: UI component explorer for frontend developers
Storybook is an open source tool for building UI components and pages in isolation. It streamlines UI development, testing, and documentation.
1 Reply
I'm pretty noob at development, but the solution I use at work is a custom component library repo. Basically a git repo that I can "npm install" into any project, that contains a bunch of components that are shared among the different sites of the company. That way, we can better control updates to the components by allowing the user side to run their updates at will.