feat: Next.js 16 update

[amannn]

TODO

• Proxy or middleware?
  • Update docs? Probably only mention that proxy.ts should now be used with Next.js 16, but don't introduce API changes to next-intl yet. We might introduce an API change in the future, but with no deprecation warnings for an extended period.
• Wait for stable release
• Bump allowed peer dependency version
• Link to learn.next-intl.dev changelog

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
next-intl-docs	Ready	Preview	Comment	Oct 10, 2025 8:39am
next-intl-example-app-router	Ready	Preview	Comment	Oct 10, 2025 8:39am
next-intl-example-app-router-without-i18n-routing	Ready	Preview	Comment	Oct 10, 2025 8:39am

[l-you]

@amannn
I upgraded my app to Next.js 16.
Website and localisation works, BUT logs are polluted.

 ⨯ Error: Cannot find module '../../dictionaries/_next.json'
    at moduleContext (.next/server/chunks/ssr/[turbopack]_runtime.js:259:19)
    at moduleContext.import (.next/server/chunks/ssr/[turbopack]_runtime.js:275:22)
    at Module.D [as generateMetadata] (.next/server/chunks/ssr/_37fe6ccb._.js:2:22595) {
  code: 'MODULE_NOT_FOUND',
  digest: '4171074594'
}

Any idea what could cause it?
This is part of code in getRequestConfig. Seems like next-intl/plugin pass _next URL path of static file to the getRequestConfig locale property.