Once added run the following command: npm run bundle-report.
![how to run webpack cli how to run webpack cli](https://blog.kakaocdn.net/dn/TGmDt/btq103peClz/KbaYDPcWdtuhUjKg87xID1/img.png)
"bundle-report": "webpack-bundle-analyzer dist/stats.json"
HOW TO RUN WEBPACK CLI INSTALL
![how to run webpack cli how to run webpack cli](https://www.valentinog.com/blog/static/77fd1fd5a3252c01c4aea6c0ea59fea7/c1b63/webpack-guide.png)
In this post we will use the Angular CLI and a few simple commands to get a detailed report about the Angular application bundles we ship to production.
![how to run webpack cli how to run webpack cli](https://img.codeshelper.com/upload/img/2021/03/12/qt3knmyjro37396.png)
For our apps to stay fast, we need to make sure they stayed small (250kb or less is a good goal) and loaded at the appropriate times.
HOW TO RUN WEBPACK CLI DOWNLOAD
Not only are they slower to download but also more time-consuming to evaluate and execute by the browser. Large JavaScript bundles are a surefire way to lose user engagement. But with our web apps becoming ever so increasingly complex how we can know what gets bundled into our apps? How do we track the size of the bundles? We want to make sure we don't send too much JavaScript all at once and slow down our apps. Having a high performing web app is always a top priority. This post has been updated to use the latest best practices with the Angular CLI which can be found here.