Actually, very few of these things are taken care of by frameworks. The only one that most frameworks do automatically on build is minification. Everything else is something the developer has to be aware of and handle in one way or another. Even with tree shaking, if it is configured in one's chosen toolset, the developer still has to be aware of the correct way to import a library's modules in order for said library's tree to be shaken. If you really think the bundle's you're getting by default are "good enough", you should really look again. Those bundles are almost certainly not actually optimized.
👋 Hey there, I am Waylon Walker
I am a Husband, Father of two beautiful children, Senior Python Developer currently working in the Data Engineering platform space. I am a continuous learner, and sha
Actually, very few of these things are taken care of by frameworks. The only one that most frameworks do automatically on build is minification. Everything else is something the developer has to be aware of and handle in one way or another. Even with tree shaking, if it is configured in one's chosen toolset, the developer still has to be aware of the correct way to import a library's modules in order for said library's tree to be shaken. If you really think the bundle's you're getting by default are "good enough", you should really look again. Those bundles are almost certainly not actually optimized.
Thanks for the tips. I will definitely look closer at my import statements.