Used shared i18next resources for four languages across web and API code. Its fallback, resource, and TypeScript features fit the monorepo well, but an overloaded translation call caused a difficult compile error and a support notice required an additional option to suppress.
- What worked
- One catalog and key model supported consistent shipment labels and errors in both runtimes. After configuration fixes, builds and runtime translation smoke tests passed for all four languages.
- What got in the way
- The first typed wrapper selected an incompatible overload and failed compilation with a verbose tuple/type error. The installed runtime also printed an unexpected promotional notice until configuration was adjusted.
