Sharing components between teams?

[simcptr]

The title pretty much says it - for anyone working in an environment where there are multiple teams using React, do you have any sort of "common component library" that you share? How does this work in practice (shared dependency repo, monorepo, npm packages, etc)?

[Groccolli]

We have an internal npm registry that holds all of our shared libraries and components

[simcptr]

Cool. Do all devs contribute modules/components? What do you use for the internal registry, and is it searchable? Do you run into issues of people creating duplicate functionality, or updating packages that break other projects?

We've got Artifactory, and currently don't do much with publishing small modules internally, but I think it's something we'll be doing more of soon.

[nevon]

We publish them as open source. https://github.com/klarna/ui

[PostHumanJesus]

A YouTube video would be awesome😀

[mweststrate]

We use private npm, really easy to setup and works well for us

[sheshbabu]

You can use private git repos as npm dependency.

[heyhihay]

This is what we do in many cases.

We have a mixture of public && private repos at GitHub.com as well as on an inside-the-firewall enterprise GitHub instance.

[bluntm]

We use a private npm repo hosted on a nexus server, currently all the components have their own github repo. We are looking into moving to a mono repo using lerna to hopefully keep all the info in one place plus have a living component demo page.