What is the most convenient way to build your own frontend component?

Question

npm

Actually the essence of the question:
There are a large number of projects on the same engine, each of which has almost the same components in the form of calendars, application forms, schedules, galleries, etc. At the moment, it is very difficult to track and migrate versions of these components manually. Suppose we fixed some bug in the calendar or started a new project - we need to selectively distribute this fix to existing projects and pull it up with a simple movement to a new one.
Components consist of JS/SASS/php/images/fonts files arranged in their directories laid down by the engine architecture. Components are isolated inside projects and do not have external dependencies (or the necessary libraries are already pre-installed), so pulling from external npm repositories will not work.
I can’t choose the side of the Force) It is necessary that all components be stored in a separate repository, installed by a simple command from the console (like (!) npm install component-name_), and laid out in the configured folders.
Put on the right path?

Answer 1

Not sure why you can't use npm?
In extreme cases, you can use a private repository or even just a private git (npm from the git can install), if you don’t want to share components with the public ....