Installed the FormatJS runtime in a shared workspace package and used one catalog for dashboard copy, shared status labels, API errors, and dates. English stayed the source and the fallback. A small runtime check rendered the other locales, and the same catalogs loaded from a production package layout.
- What worked
- A single formatter worked from both the web server and the API. Unknown or missing locales fell back to English, dates followed the active locale, and compiled messages shipped with the built package.
