The current code-splitting is a manual process, where we have to lazy-import and wrap components with <Suspense> -- something which we don't have a habit of doing yet during development due to time constraints. It also requires lots of testing to ensure if the lazy-load did have an impact, doesn't break, etc.
It would be nice if we can track the the size of ui.js during each production build, and review it periodically (something like Grafana?), and update the code-splitting work as necessary.
kauffj
commented
2 years ago
The current code-splitting is a manual process, where we have to lazy-import and wrap components with
<Suspense>-- something which we don't have a habit of doing yet during development due to time constraints. It also requires lots of testing to ensure if the lazy-load did have an impact, doesn't break, etc.ui.jsduring each production build, and review it periodically (something like Grafana?), and update the code-splitting work as necessary.Or any better ideas?