Heavy editor and chart code only load when you need them
PublishedIván Petrov
Two of our heaviest dependencies — our charting library and our rich-text editor — were being loaded eagerly on every admin page, even on routes that never use them. The sign-in page was shipping about 794KB of unused JavaScript for code paths that would never run.
Both libraries now code-split into their own lazy chunks:
- The charting library only loads on the stats dashboard, where it actually renders charts.
- The rich-text editor only loads when the article content step mounts.
Sign-in, the dashboard home, and the settings pages stop carrying both libraries. If you've felt the admin app warming up over the past months, this is the single biggest reason your initial loads are about to feel different.
May 5, 2026
Activity feed
- JRJacob Reed
Code-splitting the editor and chart bundles is the right architectural call. The reader experience does not need either, and the writer experience can afford the lazy load.
May 5, 2026
•Replay