Repo Architectures for Sharing Components - David Colwell

As UI developers we'll eventually come across situations where we want to break out a specific subset of code we're working with into it's own separate project so it can be shared or worked on as something independent of what we consider the primary app(s) we're working on. This could be as simple as a shared UI component library, more complex such as functional or utility modules we want shared across multiple projects, or could even be simply developer tooling and configuration we want to ensure is consistent across all our active projects. The possibilities go well beyond the standard "UI component library" most might immediately think of when talking about creating shared libraries from part of your app code. That said, it's important to understand the potential value as well as challenges this kind of decision might bring.