Development environment works, but Route /_not-found couldn't be rendered statically error in production builds.

[jooy2]

Description

Hello, first of all, I would like to thank you for developing next-intl.

While applying this module to a project that uses Next.js app router, I faced the following problem:

In the development environment, the translation works fine without any errors, but when you do next build for production, the build fails with the following error:

Generating static pages (0/4)  [    ]Error: Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the `unstable_setRequestLocale` API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router/with-i18n-routing#static-rendering
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:72824
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    ... 5 lines matching cause stack trace ...
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75105
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75620 {
  digest: '1848317962',
  [cause]: n [Error]: Dynamic server usage: Route /_not-found couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
      at c (/Users/user/nextapp-template/.next/server/chunks/555.js:37:126506)
      at d (/Users/user/nextapp-template/.next/server/chunks/555.js:37:79383)
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:72726
      at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
      at u (/Users/user/nextapp-template/.next/server/chunks/555.js:37:73566)
      at get locale [as locale] (/Users/user/nextapp-template/.next/server/chunks/555.js:37:74243)
      at /Users/user/nextapp-template/.next/server/app/_not-found/page.js:1:7753
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:74250
      at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75105 {
    description: "Route /_not-found couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error",
    digest: 'DYNAMIC_SERVER_USAGE'
  }
}
Error: Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the `unstable_setRequestLocale` API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router/with-i18n-routing#static-rendering
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:72824
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    ... 5 lines matching cause stack trace ...
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75105
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75620 {
  digest: '1848317962',
  [cause]: n [Error]: Dynamic server usage: Route /_not-found couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
      at c (/Users/user/nextapp-template/.next/server/chunks/555.js:37:126506)
      at d (/Users/user/nextapp-template/.next/server/chunks/555.js:37:79383)
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:72726
      at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
      at u (/Users/user/nextapp-template/.next/server/chunks/555.js:37:73566)
      at get locale [as locale] (/Users/user/nextapp-template/.next/server/chunks/555.js:37:74243)
      at /Users/user/nextapp-template/.next/server/app/_not-found/page.js:1:7753
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:74250
      at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75105 {
    description: "Route /_not-found couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error",
    digest: 'DYNAMIC_SERVER_USAGE'
  }
}
Error: Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the `unstable_setRequestLocale` API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router/with-i18n-routing#static-rendering
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:72824
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    ... 5 lines matching cause stack trace ...
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75105
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75620 {
  digest: '1848317962',
  [cause]: n [Error]: Dynamic server usage: Route /_not-found couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
      at c (/Users/user/nextapp-template/.next/server/chunks/555.js:37:126506)
      at d (/Users/user/nextapp-template/.next/server/chunks/555.js:37:79383)
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:72726
      at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
      at u (/Users/user/nextapp-template/.next/server/chunks/555.js:37:73566)
      at get locale [as locale] (/Users/user/nextapp-template/.next/server/chunks/555.js:37:74243)
      at /Users/user/nextapp-template/.next/server/app/_not-found/page.js:1:7753
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:74250
      at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
      at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75105 {
    description: "Route /_not-found couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error",
    digest: 'DYNAMIC_SERVER_USAGE'
  }
}

Error occurred prerendering page "/_not-found". Read more: https://nextjs.org/docs/messages/prerender-error

Error: Usage of next-intl APIs in Server Components currently opts into dynamic rendering. This limitation will eventually be lifted, but as a stopgap solution, you can use the `unstable_setRequestLocale` API to enable static rendering, see https://next-intl-docs.vercel.app/docs/getting-started/app-router/with-i18n-routing#static-rendering
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:72824
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    at u (/Users/user/nextapp-template/.next/server/chunks/555.js:37:73566)
    at get locale [as locale] (/Users/user/nextapp-template/.next/server/chunks/555.js:37:74243)
    at /Users/user/nextapp-template/.next/server/app/_not-found/page.js:1:7753
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:74250
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75105
    at /Users/user/nextapp-template/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:12:185364
    at /Users/user/nextapp-template/.next/server/chunks/555.js:37:75620
 ✓ Generating static pages (4/4)

> Export encountered errors on following paths:
        /_not-found/page: /_not-found

It looks like there is already an issue with the same problem as this one. However, the issue is closed and none of the solutions there worked for me:

#521

There is a reproducible project included in the reproduction course below: (https://github.com/jooy2/nextapp-template)

It's using Next.js 14.2.15, and there are third-party libraries like Material UI and Redux, but I've minimized their use in the project above to a single page.

Could you please check what part of my project is causing the problem, I would like to know if this is due to something I'm doing wrong or if it's a bug in next-intl.

Thank you.

Verifications

• I've verified that the problem I'm experiencing isn't covered in the docs.
• I've searched for similar, existing issues on GitHub and Stack Overflow.
• I've compared my app to a working example to look for differences.

Mandatory reproduction URL

https://github.com/jooy2/nextapp-template

Reproduction description

I am using:

• Next.js 14.2.15 with App Router
• Node.js 20.12.0
• IntelliJ IDEA
• macOS Sonoma 14.6.1 (M1 Max)

Steps to reproduce:

1. Clone the following repositories: (https://github.com/jooy2/nextapp-template)
2. npm i
3. Perform npm run build.

Expected behaviour

The Next.js build should perform without errors.

[amannn]

Please have a look at the App Router example, this example has a 404 page that can be statically rendered.

As a side note, at a first glance your layout at app/layout.tsx looks fishy to me. It tries to read a locale param, but is located outside of the [locale] folder. If you compare your implementation with the example, I'm sure you can find differences like this.

I'll move this to a discussion since this is a usage question.

[ZuBB]

Just my 5c here: it would be nice to have a dedicated example for the 'static render' case

[escwxyz]

It is weird that I also got this error in dynamic mode, when i didn't throw any notFound.

Error getting user locale: Error: Dynamic server usage: Route /_not-found couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error
    at r (.next/server/chunks/897.js:1:5193)
    at m (.next/server/chunks/472.js:1:3303)
    at f (.next/server/chunks/534.js:1:5075)
    at <unknown> (.next/server/chunks/534.js:1:5787)
    at <unknown> (.next/server/chunks/211.js:1:215274)
    at <unknown> (.next/server/chunks/211.js:1:215595)
    at <unknown> (.next/server/chunks/211.js:1:171946) {
  description: "Route /_not-found couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/messages/dynamic-server-error",
  digest: 'DYNAMIC_SERVER_USAGE'
}

Route (app)                                 Size  First Load JS
┌ ƒ /                                     284 kB         581 kB
├ ƒ /_not-found                          1.01 kB         158 kB
├ ƒ /api/auth/[...all]                     140 B         158 kB
├ ○ /robots.txt                            140 B         158 kB
└ ○ /sitemap.xml                           140 B         158 kB
+ First Load JS shared by all             157 kB
  ├ chunks/2e38e746-74c8e043019b88ab.js  56.2 kB
  ├ chunks/9694-42657556e497f49c.js      44.5 kB
  ├ chunks/e74b94c5-5917389408f23763.js  54.1 kB
  └ other shared chunks (total)          2.59 kB 

[alyatwa]

for me I just passed msgs to NextIntlClientProvider
<NextIntlClientProvider locale="ar" messages={messages}>
It worked but i do not know whyy