Spike : Investigate how to expose the common components outside the project to be used in another project

[brindasasi]

Problem

Our team involves in building diff applications time to time. We also maintain a library of core components that can be re-used across all the projects.

Proposal Instead of copy-pasting existing code to different projects, we should be able to organize our repo so that these components/api can be exposed outside the projects. Client applications can use them to serve diff purpose like building an IAP program or building an Accessibility Passport program. The idea is to begin with extracting out the common components library and we can do api and other things later on.

Deliverables

• [ ] Come up with different options how we can expose our common components library so that another project can reuse it

[gggrant]

Transfer to accessibility passport board.

[JoshBeveridge]

I used to do this with Clone back in the day, where components were individually packaged as JS modules that could be installed through NPM and imported into any project. I'd recommend taking a monorepo approach for your own sanity's sake, but the idea would be the same for React components, I believe.