Hi Damien, Start with an "empty" shell/demo/kitchen-sink app, in which you can pull in "dynamic" HTML. Then use the CLI to create libraries, and use NPM to publish those. You might need a private NPM namespace or your own in-house NPM(like) server. The big win of this way is that all tooling is already geared towards this way of working. Decide if you want to push out single elements, or small libs.
When I'm working on a new thing, I'll first create it in the shell app, build a small demo/test for the thing. This way I can easily build/iterate on it. When it's ready, I'll move it over to a library. (you can build it in a library from the get-go, but it takes way more steps to test, iterate then) Create those elements as Angular Elements (this is optional, but it will pay off in the long run.) -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. To view this discussion on the web visit https://groups.google.com/d/msgid/angular/77c8ec85-3fd5-41fd-96a7-7465ca91b9a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
