Optimize AgileTs for tree-shaking
bennoinbeta opened this issue · comments
🆕 Feature Request
❓ Is your feature request related to a problem?
Big bundle size
📄 Describe the solution you'd like
As a user I want my application to be as small as possible,
thus, I don't want to have unused functionalities of AgileTs in my production build.
📃 Describe alternatives you've considered
No alternative
➕ Additional Notes
- https://dev.to/lukasbombach/how-to-write-a-tree-shakable-component-library-4ied
- https://redd.one/blog/building-a-tree-shakable-library-with-rollupjs
- https://developers.google.com/web/fundamentals/performance/optimizing-javascript/tree-shaking
- https://blog.theodo.com/2021/04/library-tree-shaking/ 💪
💪 TODO
- Treeshake Collection
- Treeshake Computed
- Treeshake Logger (-> only logCodes in prod instead of whole messages)
- Treeshake unused Hooks/HOC's
- Treeshake Storage functionality
an interesting thread
webpack/webpack#9337