onError seems to not have any effect?

[stavros-k]

I'm doing nextjs SSG builds (fully static)
I have this i18n/request.ts. (i18n without routing / app router)

export default getRequestConfig(async ({ requestLocale }) => {
    let locale = await requestLocale;
    // Validate that the incoming `locale` parameter is valid
    if (!general.supported_langs.includes(locale as any)) notFound();
    return {
        locale: locale,
        messages: (await import(`../src/config/messages/${locale}.json`))
            .default,
        timeZone: "Europe/Athens",
        onError: (error) => {
            if (error.code === IntlErrorCode.MISSING_MESSAGE) {
                throw new Error(`Missing message for locale: ${locale}`);
            }
        },
    };
});

During npm run build, I'm still seeing the default error message on the console, I'd expect an error thrown and build to fail.

Error: MISSING_MESSAGE: vouchers (en)
    at <unknown> (.next/server/chunks/451.js:11:144229)
    at t.createBaseTranslator (.next/server/chunks/451.js:11:144279)
    at <unknown> (.next/server/chunks/451.js:11:151544)
    at <unknown> (.next/server/chunks/451.js:11:151530)
    at t.useTranslations (.next/server/chunks/451.js:11:151723)
    at <unknown> (.next/server/chunks/451.js:11:49972)
    at <unknown> (.next/server/app/[lang]/[...page]/page.js:31:1333) {
  code: 'MISSING_MESSAGE',
  originalMessage: 'vouchers (en)'
}

I've tried looking at the docs but couldn't find anything

Any ideas?

[amannn]

Hey, this is unfortunately a bit confusing & cumbersome currently to get right and something I'm working on improving. Please see #1285.

If you'd like to take next-intl@v4-beta for a spin, it's slightly easier there to get right.

I'm currently waiting for better support in Next.js to register client side error handling, hopefully the current API can be deprecated in the future for something that is easier to work with and aligns with user expectations.