![mui themes symlinker mui themes symlinker](https://i.ytimg.com/vi/W-QasNYJ-3Y/maxresdefault.jpg)
Be versionable using Semantic Versioning.Have components that are able to be displayed and interacted with on an internal (or external) website without having to set the library up locally.Bundle and transpile the components and be able to be published to an internal (or external) NPM registry as a single package.Have each component thoroughly tested (using Jest/React Testing Library).Use TypeScript (and bundle/export TypeScript types).There were a number of requirements I had for the component library. It''ll also cover how you can build your own React component library! Table of Contents I wrote this article to share my experience around researching and building the component library.
#MUI THEMES SYMLINKER HOW TO#
I thought it would also be great to learn how to create, manage and help adopt a component library used in production across multiple engineering teams and projects. I strongly believed the component would help speed up front-end development by removing the need to write/copy paste components over to new projects. This component library would enable teams to pull down an NPM package, import components, provide some props and have their components ready to use.
![mui themes symlinker mui themes symlinker](https://i.pinimg.com/originals/41/ad/a0/41ada0775c84feb8991185206ccbd06d.jpg)
I saw a real need for an internal component library. Components across projects were created from scratch, rewritten or copy pasted over each time. Up until now, we had no shared style-sheets or components.
![mui themes symlinker mui themes symlinker](https://wallpapercave.com/wp/wp6312032.jpg)
Each of these projects are designed by our internal designer and had a lot common with them (same inputs, buttons designs etc). At work we have a number of front-end projects that are worked on by different project teams.