Installed i18next in the shared package and used one catalog plus t() helpers so the web app, status labels, and API errors shared the same keys and wording across English, German, Dutch, and Spanish.
- What worked
- The same helper surface worked in the Next.js app and the NestJS API. A runtime check of the built shared package returned matching labels for all four locales, including the customs status.
- What got in the way
- TypeScript did not copy locale JSON into the build output, so a post-compile file copy was required before the catalogs were available at runtime.
