$ the-wire · showcase
PHOENIX ROUTES GET 3X FASTER COMPILATION, BUT YOUR DEAD ROUTES ARE NOW ALIVE
By RepoJournal · Filed · About Elixir & Phoenix · Composed from the cited sources · methodology
1 person shipped this
Phoenix's router compiler just got a massive speed boost by grouping routes by HTTP verb, but it's exposing bugs you didn't know you had.
The Phoenix team shipped a compilation optimization [1] that can cut router build times by 3x on large applications. The catch: routes are now matched strictly by verb, which means dead routes (like a `get "/foo"` after a `match "/foo"`) will suddenly start matching. This isn't a breaking change you should fear; it's exposing code that should never have existed. Fix it by removing the duplicate routes.
On the LiveView front, v1.2.5 shipped [3] with a critical fix for custom UploadWriters [2]. Previously, if your upload handler returned an error, it would crash the entire LiveView instead of just failing the upload. Now it shuts down gracefully, letting the view survive the error. The same release [3] also improved deprecation warnings for TagEngine so you'll actually know which file needs fixing.
Both improvements land in stable channels today. The router change requires a glance at your route files; the upload fix requires nothing from you unless you have custom writers.
Action items
- → Upgrade Phoenix to latest and audit routes for verb conflicts phoenixframework/phoenix [plan]
- → Upgrade Phoenix LiveView to v1.2.5 to protect uploads from writer errors phoenixframework/phoenix_live_view [plan]
- → Check your custom UploadWriter implementations and test error paths phoenixframework/phoenix_live_view [monitor]
References
- [1] Split routes by verb during compilation ↗ phoenixframework/phoenix
- [2] Stop upload channel with {:shutdown, :closed} on writer error so the LiveView survives (#4320) ↗ phoenixframework/phoenix_live_view
- [3] v1.2.5 ↗ phoenixframework/phoenix_live_view
