Support 3rd party aem component libraries

[CodeByAlex]

Right now the htl engine works with custom components but not proxy components. We need to provide this capability so that people can use the core components

[CodeByAlex]

@tripodsan from the Discord chat:

I think it should work like this:

• we create a npm package that contains all the aem core components and stories. we already started this for Text,List,Accordion.

then a user you would:

• npm add aem-core-components-storified
• in components decorator: [ require('aem-core-components-storified').components]
• in models decorator [ require(aem-core-components-storified).models]
  (something along those lines)

and then just use the normal sling:resourceSuperType in his custom component. and import / extends the model if he needs eg:

import Text from `aem-core-components.storified`.models;

class MyText extends Text {
}

[CodeByAlex]

The above however only supports a single library type - it would be great to support any 3rd party library...thinking of a solution for that. We can easily get the css and html for a component by making a one time call to a live aem instance using our cli tool ( we would have to add the capability) - but how would we get any information about the java models (assuming the libs are written using java models - if they are using javascript, it becomes very easy to include them)

[CodeByAlex]

We now have a path forward to achieve this