Error: Cannot find module "xxx.json"

[ManucherKM]

Description

Hey, everybody. I have encountered a rather strange problem. When switching to an unknown "locale" the console displays 'Error: Cannot find module "xxx.json"', but the application works normally.

Error screenshot:

Page:

I apologize in advance. When trying to simulate this error in a simplified version, I failed. But if it's not a problem, here's my pet project repository: https://github.com/manucherkm/quickfile. So, how can I solve this problem? Otherwise I am happy with the package so far.

Mandatory reproduction URL (CodeSandbox or GitHub repository)

https://github.com/manucherkm/quickfile

Reproduction description

Steps to reproduce:

1. Open the downloaded project
2. run npm i
3. Add a .env.local file with the contents NEXT_PUBLIC_API_URL=http://localhost:5000 and NEXT_PUBLIC_CLIENT_URL=http://localhost:3000
4. run npm run dev
5. Navigate to the non-existent locale /sdasda
6. Look in the console of the IDE/Code Editor.

Expected behaviour

Expected behavior: Error-free console and working project.

What we have now: A working project, but with an error in the console.

[flux0uz]

We have similar errors in our logs.

With this matcher for the middleware:

export const config = {
  matcher: [
    // Skip all paths that should not be internationalized
    "/((?!api|_next|_vercel|.*\\..*).*)",
    // Match all pathnames within `users|songs|artists`, optionally with a locale prefix
    "/([\\w-]+)?/(songs|artists|users)/(.+)",
  ],
}

We use next-intl@3.3.2 and next@14.0.4

[FourwingsY]

Same error here.
I just write some workarounds for this.

export default getRequestConfig(async ({ locale }) => {
  if (!supportedLocales.includes(locale)) {
    return { messages: (await import(`./${defaultLocale}.json`)).default };
  }
  return {
    messages: (await import(`./${locale}.json`)).default,
  };
});

[amannn]

There was an update to this in #742. The solution is pretty much what @FourwingsY is suggesting here: The locale should be validated in i18n.ts. This is now suggested in the docs moving forward.

Thanks for raising this!