Build a component library for Next.js w/ shadcn/ui
Hi all,
so as per the topic, I am looking to build a component library for my company so I will be able to easily import the component I need with a simple
npm i
I already found some information on how set this up thanks to this article and the only thing I found specific about React Server Components is this article and nothing more.
Now I know that I am probably falling for the analysis paralysis syndrome, but I like to have a clear plan of action before do something new (yes, this would be the first time I build a component library that I'll publish on NPM 😊)
Since I will use shadcn/ui library, I was also studying how he managed to create the CLI since it looks to me an easier approach because instead of relying on my own packages hidden in the node_modules/ folder, I should be able to pull the components one by one and even customize them in case I need a quick fix.
I'll start to experiment myself, but if someone of you already has experience with this approach it would be great if you want to share your knowledge.How to Build a React Component Library
In this tutorial, we will walk through how to build and publish a React component library so it can be used across multiple React projects.
1 Reply
Is this question too silly or no-one had this need yet?