ThePalaceProject / web-patron / 32397845389

30%

push

github

Make i18n config visible to containerized app (PP-4961) (#185)

## Description

Pass the `next-i18next` config to `serverSideTranslations` explicitly
instead of relying on it being found on disk at request time.

- Every page builds its i18n props through one helper, so this is a
single call site.
- Adds a type declaration so the CommonJS config can be imported under
`allowJs: false`.
- Also copies the config into the runtime image in case a future call
site omits it.

## Motivation and Context

Every server-rendered page returned an error page in the dev deployment,
and locally when running the standalone server directly.

Left to itself, next-i18next resolves `./next-i18next.config.js` against
the working directory on every render. Nothing in our code referenced
the file, so it only ever reached the standalone bundle because Next's
file tracer inferred it. Up until Next 16.3.0 replaced it (`@vercel/nft`
0.27.1 -> 1.10.2). Now it no longer emits "working-directory-relative"
assets discovered in dependency code, and the file stopped being copied.
Importing the config removes the dependency on both the tracer and the
working directory.

[Jira PP-4961]

## How Has This Been Tested?

- Manual testing in local dev environment. Specifically:
- Production build run through the standalone server with the config
file absent: the multi-library home page, library pages, and the `/en`
locale route all render with translations and no errors.
- `npm run dev` verified for the same routes, with the language selector
flag both on and off.
- All tests / checks pass locally.
- [CI tests /
checks](https://github.com/ThePalaceProject/web-patron/actions/runs/32385569818)
pass.

## Checklist:

- [x] I have updated the documentation accordingly.
- [x] All new and existing tests passed.

326 of 1467 branches covered (22.22%)

Branch coverage included in aggregate %.

705 of 2049 relevant lines covered (34.41%)

9.24 hits per line