When served, the compiled app.js is a behemoth 10MB file, which is loaded along with other 25+ assets on the first loading of the website (even before the app to be able to decide whether to show the login page or the blank template page).
This would throttle performance & may end up chocking the application as it grows larger. FWIW, it's just beyond the MVP at this point, and browser already eats processor's soul to process the JS.
We should rather go more modular way of serving JS, depending on the requirement(s) of the current view (and not serving everything we have, up front, 90% of which may be needed or not).
When served, the compiled
app.jsis a behemoth 10MB file, which is loaded along with other 25+ assets on the first loading of the website (even before the app to be able to decide whether to show the login page or the blank template page).This would throttle performance & may end up chocking the application as it grows larger. FWIW, it's just beyond the MVP at this point, and browser already eats processor's soul to process the JS.
We should rather go more modular way of serving JS, depending on the requirement(s) of the current view (and not serving everything we have, up front, 90% of which may be needed or not).