Large Bundle Size - Angular
See original GitHub issueI tried compiling the angular 6 project with and without devexteme-angular. I just used simple customer grid in the app.component and build the project using ng build --configuration production
. main.*.js bundle seems to be too large for such a small demo app. I did set AOT, buildOptimizer and other configurations for the prod.
Versions: “devextreme”: “^17.2.7”, “devextreme-angular”: “^17.2.7”
Here’s the screenshot
Please let me know if I’m missing anything in the configuration or any optimization strategy needs to be done.
Cheers, Aniket
Issue Analytics
- State:
- Created 5 years ago
- Reactions:16
- Comments:63 (2 by maintainers)
Top Results From Across the Web
Optimize Angular bundle size in 4 steps | by Siyang Kern Zhao
Step 3: Analyze your Angular bundle If your bundle size does get too big you may want to analyze your bundle because you...
Read more >Angular - How to improve bundle size? - Daniel Kreider
Here are 5 ways you can reduce the bundle size. And make it load faster. ⚡️ · Investigate your app module. It has...
Read more >Dev Discussions: How to Reduce your Angular Bundle Size ...
Bundle reduction tip #1: Use tree shaking · Faster testing · Better debugging · Improved CSS class and style binding · Improved type...
Read more >How to decrease prod bundle size? - angular - Stack Overflow
Firstly, vendor bundles are huge simply because Angular 2 relies on a lot of libraries. Minimum size for Angular 2 app is around...
Read more >Reduce the Bundle Size of Your Angular App | Pluralsight
The most straightforward means of reducing your bundle size is to ensure that you are using the latest version of the Angular framework....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @all,
Let me share our current progress with you. We prepared our codebase migration to ES6 modules and these modules will be available in v20.2. Our next goal is to properly support tree shaking and perform code splitting. We have plans to introduce tree shaking in the next major release (v20.2) if it all goes well. As for the code splitting, this task requires more time and I can’t give you any estimates.
my final decision was just don’t use this library. Its optimization is bad.