How do you deploy angular projects?

Question

Angular

I'm looking at Angular. I do simple things on angularJS. Convenient, nice. We don't do anything big, so that's enough. But already obsolete. Went to watch ANGULAR. And here's the question. When compiling, we get a very strange construction that you cannot drive into git. But what about? There are several dozen sites with an admin panel. In the admin panel, let's say I'm making some tool in Angular. So what? Should I drive this compiled blizzard into the repository and update the code from this repository everywhere? I see the only way out is to send the source codes and the compiled part to the repository. And I understand that when compiling angular, it gives unique names to all project files. That is, each time to delete the compiled and re-add?
Please share how you deal with this. When one project with a bunch of code in Angular is generally understandable. There it seems you can set up auto-assembly. I'm sure it's possible. And if this is a small thing in Angular, which rolls out on 50+ projects. What to configure autoassembly on each? Overall, I'm a bit confused. Tell me who is doing it.

Answer 1

Nothing compiled in the turnip should be kept - only the source code. Compile - directly on the servers.

Answer 2

My choice is GitLab. It has CI with convenient runners.
Not ideal, but for my tasks in Angular and Nodejs - through the roof. When you start googling, don't leave dockers out.

Answer 3

You should not store artifacts in turnips, only source codes. Deploit naturally entirely. If there are reusable parts, then take them out to library projects and publish them to npm. Front build results can also be compiled into a docker image if you use one.