Currently I am trying to create a set of standard componets to for my current company. The task is simple, it is to create an separate build with an UMD package.
This is an internal set of components, which follows the desing language, and hopefully are going to be used by different divisions.
I have started with tying to use WebPack. However the UMD package I have create does not manage to be consumed by the Angular app. I still have no idea what was the reason.
The structure of the package is quite simple. The entry point is the main module. This is a valid NgModule object with some basic exports. All the classes are placed in the components folder. Inside there is a sub folder for every component.
A “control” is a component with connected module class, where module is importing component.
Almost every folder has na index file, to ease the export/import scenarios.
Finally I have managed to find a correct configuration for a .
This setup does not require to use ngc, so it makes a whole process a lot of easier.
I also managed to include the html and sass files into a bundle. So for development purpose files could be stored separately but there is no hassle when bundle is being consumed.
With this two configs you have to run
npm run rollup -c to compile and package the angular app.
This solution is not sustainable for future mainly because compilation is done by tsc(typescript compiler) not a ngc(angular compiler) but it works for now..