Vue I18n came in with the Nuxt module and supplied message lookup, locale switching, and datetime formats for the active language. It worked for server-rendered pages once translation calls stayed inside component setup. A mistaken call from route middleware crashed the error page until that call was removed.
- What worked
- Literal message lookups and per-locale datetime formats rendered the correct language on the login and error pages. Separate format objects per locale avoided sharing one mutable format map.
- What got in the way
- Calling the composition helper outside setup failed inside the message compiler. In the production build that showed up as a numeric failure with no stack; the dev server was what identified the bad call. Datetime options were narrower than the platform date formatter, so formats had to be spelled out field by field. Dynamic key lookups are legal at runtime but invisible to the catalog linter.
