Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x] feature request
Desired functionality.
Currently, when I build out my project with ng build or ng build --prod, I see something like this:
It tells me how large my chunks and bundles are which is helpful. I can then turn this information into a useful visual to get a better understanding of what exactly is in each bundle or chunk using the source-map-explorer or the webpack-bundle-analyzer. However, it's kind of difficult to tell which chunk is coming from which lazy-loaded module.
I think it would be wise to include the name of the module in the file name somehow.
for example: instead of 0.9c59d5dde120b62746c2.chunk.js it would be AdminModule.0.9c59d5dde120b62746c2.chunk.js
This feature would be helpful when trying to understand the module architecture of your application.
Bug Report or Feature Request (mark with an
x)Desired functionality.
Currently, when I build out my project with
ng buildorng build --prod, I see something like this:It tells me how large my chunks and bundles are which is helpful. I can then turn this information into a useful visual to get a better understanding of what exactly is in each bundle or chunk using the source-map-explorer or the webpack-bundle-analyzer. However, it's kind of difficult to tell which chunk is coming from which lazy-loaded module.
I think it would be wise to include the name of the module in the file name somehow.
for example: instead of
0.9c59d5dde120b62746c2.chunk.jsit would beAdminModule.0.9c59d5dde120b62746c2.chunk.jsThis feature would be helpful when trying to understand the module architecture of your application.