Organization of a corporate repository of angular components?

Question

Angular

The background is as follows - there is a small IT company that employs several front-end teams. They do different projects, but at the same time periodically solve the same tasks, create similar components.
The idea of ​​creating a corporate repository has matured - where each team would post their solutions, and the rest could not reinvent the "bicycle" anew, but take it and use it. It is also possible to send requests for improving components.
Actually the question is - how would you solve such a problem?

Answer 1

You can specify a git repository as the bower dependency source.
Get yourself a gitlab.