ng-dynamic-component VS UAT-DynamicViewKit

Also, if you just want to have this functionality, I can recommend ng-dynamic-component.

I'm currently using library: https://github.com/gund/ng-dynamic-component

Code of the demo.

I've got an old repo that does the things you are describing.

What I can point you towards is my own library for working with these. The documentation for using my dynamic animations is part of my dynamic toolkit which you can use as an example. The code for these dynamic animations is extensive as my goal was to implement a state machine that mirrors the way the animations component field works. So my dynamic animations also works off of states and animated transitions between them.

You can pretty easily wrap the suggested code up into your own desired functionality. For instance here is my stab at a generic reusable dcl. But from what I know you still end up with the boiler plate from the docs at some level.

But if you want to try the needlessly complex route then here is the service in a library I wrote. The code is abstracted there so it might not help a lot but if you do want to dig through that entire section and look at how I use a view container ref for where things can be placed, attach template ref directives to individual pieces of content, the small demo just to show that it works, and see the demo actually executing then by all means knock yourself out.

This isn't exactly the same, but here I am allowing a custom definition of a resource for my module, which overwrites the default, if one is defined in the code consuming my library.

If you would like you can look at the work I've done with the animation builder and an extremely simple demo using it that does not have the issue you are seeing. Also here is the code to that demo.

So I'm going to skip over more details about dynamic components and instead point you towards my deck library. It has far more documentation than I could write here which shows more or less how I approached a very similar problem.