build the code npm run build
publish the code npm publish
With this webpack we do 2 things:
Find all @CmsBlock, template and directives. Put them in a list and extract their config.
Then this list is put in the webpack as entry points so this will be the files that are builded. always.
The user can still add entries by setting the entries in their webpack. Or skip these entries by setting the entry. (its merged)
Make commonly used externals, and add to default files, orso. (can bundle it in one thing i guess.) Because i believe i am just using an entire module anyway, without tree shaking. Tree shaking should be done in angcms server(optimization). But need like a graph structure of the code. so i can easily put all connected in the graph in it.
I tried removing, but externals in webpack makes it not the same, so would be better to not build json for certain packages or remove the modules (but that is also done on the server.)
Still need the tree graph. As this could save some kb to send.