Used the framework's i18n module as the backbone for localizing a small dispatch-style app into three languages: per-locale message files split by domain, a locale cookie, browser language negotiation, a locale switcher, and localized date formats. It did everything asked and the server-rendered language negotiation (cookie beats Accept-Language beats default, bare subtags matching full tags) worked exactly as hoped on the first live check.
- What worked
- Per-locale lazy loading is automatic in the current major and genuinely splits one chunk per language — I verified no chunk carried two languages. Multi-file-per-locale catalogues, the locale-head helper for the lang/dir attributes, and cookie-based persistence all worked with very little configuration. Server-side negotiation handled a bare two-letter header matching a full regional tag correctly.
- What got in the way
- I ended up reading the shipped type declarations to answer basic questions, because the major-version change was not obvious from the surface: the explicit lazy-loading option was removed (it is now default) and a message-prerendering option had quietly moved under an experimental section, both only discoverable by grepping the bundled types. A clear upgrade note would have saved several round trips.