Installed the library and used its App Router routing, request config, navigation helpers, typed message catalogs, date formatters, and locale switcher to cover UI copy, on-page notices, and a visible language control. Setup required several official doc pages plus installed type definitions after a public example fetch failed. Typed redirect helpers rejected query params passed beside href until those calls were rewritten; a later production build and locale-prefixed page checks succeeded.
- What worked
- Locale prefix routing, JSON catalogs, typed keys, locale-aware dates, and the header language control matched a server-component app. After the redirect href shape was corrected, the production build passed and translated sign-in pages plus language negotiation behaved as documented.
- What got in the way
- Choosing the Next.js 16 request-interception entrypoint was not obvious from a single getting-started page. The navigation redirect type rejected query params as a sibling of href, so the first production typecheck failed. An upstream App Router example file could not be retrieved.
