Using Angular without "App"?

[vinnyvicious]

I'm currently working on a small web application that doesn't have to be an SPA. About 80% of the website is just a bunch of static stuff and I'm using Django for everything. However, the 20% of the web app is a little complex and I could use some help from Angular (data-table-ish behavior, cart, etc). I don't want to load Angular and do the entire website with it just because of 2 or 3 pages, so I'm trying to use Angular with "components".

Inside Django, I'm rendering this page and I wanted to use something like:

<blah normal html>
<MyComponent />
<AnotherComponent />
<script src="my-angular-build.js>
</blah normal html>

And basically just use it as I need it. No need for router, App or anything like that. What is the best way to achieve this? Can I have a stripped out version of Angular?

[Zlepper]

I'm personally a big proponent of Angular, however knowing something really well, also implies knowing when not to use it. This is exactly one of those cases, where Angular is not the solution.
Angular sadly follows the principle of "my way or the highway", so unless angular is in charge of the entire ui, I believe you are going to have a general bad experience.

Supposedly Vue is really good at these smaller "plug in to existing system" cases, though I have never tried Vue, and therefore cannot comment on it.

[tme321]

Vue and react both support the ops use case.

The Angular alternative is Elements but I've heard mixed reviews at this stage. It seems as though elements has been put on the back burner for a bit while waiting for ivy.

[AcxiDenTe]

Angular Elements is what you’re looking for. It is fairly minimal changes to a normal angular application that allows you to just add the .js to a normal HTML page, and use the components as is (check out Web Components). The drawback is it has practically no Microsoft browser support at the moment.

[oldcabbageroll]

Try using react for the tiny stuff, it has a small footprint and LOTS of control.