Legacy Angular App - Source Map Analysis
NOTE: This advice relates to the legacy Angular frontend, which we are deprecating and is included for reference purposes until that work is complete.
As the Supervision Frontend logic runs in the browser, all libraries needed by the application are bundled into a single JavaScript file.
Running source-map-explorer lets you see the libraries and Angular modules that make up these JS files.
This can be useful for identifying unused libraries that are still being bundled, or identifying overly large libraries that are bloating these files
Any reduction in the size of these libraries should be a slight improvement for the end user, as it will download quicker on an initial load and potentially run faster in low resource situations
Running Source Map Explorer
Source map explorer can be run either through make
make supervision-generate-source-map-analysis
This will generate a html file that displays the makeup of the js files.
To see a breakdown of internal modules, you must check the “Show content of concatenated modules” checkbox from the menu in the top-left.
You can zoom in on directories to see the detailed sizes of each of their files.