The auth SDK no longer ships in the entry chunk
ReleasedTomislav Babic
Our authentication SDK was bundled into the entry JavaScript chunk of the admin app, meaning every visitor — including the ones who never reach a sign-in form — downloaded and parsed the entire auth library on first paint. That was wasteful.
The auth SDK is now lazy-loaded out of the entry chunk and only pulled in when a route actually needs it. The bundle savings are most felt on routes that authenticated users hit repeatedly (the dashboard, the editor, the stats page) since the auth SDK is now cached separately from the rest of the app code.
If you have ever felt the dashboard take a beat too long to wake up on a cold visit, you should notice it pop in noticeably faster.
May 5, 2026
Activity feed
Tomas ReyesPulling the auth SDK out of the entry chunk is the kind of perf win that compounds. Especially helpful for visitors who never reach a sign-in screen — they were eating the cost for no reason.
May 19, 2026
•Replay