Type-safe getTranslations namespace option

[CarrettaRiccardo]

With a basic setup of next-intl and nextjs, i came across the documentations to enable static rendering.

Following the last step, it is required to provide locale and namespace to getTranslations, like so:

  const { locale } = await params;

  const t = await getTranslations({ locale, namespace: 'HomePage' });

The above namespace is not type-safe:

Even tho the usual getTranslation way has it:

Not sure why, as it seems to correctly infer the namespaces in the type definition and when hovering the function:

Tried a couple different ts versions (5.8.2, 5,9)

---

Using next-intl 4.0.2, with "Messages" strictly-typed

[amannn]

From my experience, autocomplete somehow doesn't really work for namespace when using the object form of getTranslations. However, type errors are reported correctly.

In the future, once rootParams is a thing, the object form of getTranslations will not be necessary in almost all cases (including static rendering). So hopefully this problem should not be gone in the future.