Next-intl breaking static rendering #1960

zacBkh · 2025-07-19T12:37:41Z

zacBkh
Jul 19, 2025

Hello everyone!
First thanks a lot for this amazing library @amannn

I am using next js 15.3 and next-intl v4 (without i18n), with next auth.
I have the feeling next-intl is forcing any pages to be rendered as dynamic (the build ouput proves this, with the "ƒ" symbol showing in front of my route.)

I have setup next intl routing to read from cookies like below:

import { getRequestConfig } from 'next-intl/server'
import { getUserLocale } from '../services/locale'

export default getRequestConfig(async () => {
  const locale = await getUserLocale()
  // const locale = 'en'

  return {
    locale,
    messages: (await import(`../messages/${locale}.json`)).default,
  }
})

My RootLayout is as below:

export default async function RootLayout({
  children,
}: Readonly<{
  children: React.ReactNode
}>) {
  const locale = await getLocale()

  return (
    <html lang={locale} className={font.className}>
      <Providers>
        <body>
          <ThemeProvider
            attribute="class"
            defaultTheme=""
            enableSystem
            disableTransitionOnChange
          >
            <NextStepProvider>
              <div data-vaul-drawer-wrapper="">
                <div className="relative flex flex-col bg-background">
                  <NextIntlClientProvider>
                    <NavbarsWrapper />
                    <main className="px-3 sm:px-8 my-4">{children}</main>
                  </NextIntlClientProvider>
                  <Script src="/sw-registration.js" />
                  <Toaster />
                </div>
              </div>
            </NextStepProvider>
          </ThemeProvider>
        </body>
      </Providers>
    </html>
  )
}

I understand next js switches to dynamic rendering when reading from cookies but I would like to set a default locale to still be able to render the page statically.

I would really appreciate some help as I have been looking for days about the solution, without success...

amannn · 2025-07-24T11:51:57Z

amannn
Jul 24, 2025
Maintainer

Please be sure to check out the static rendering docs.

Potentially in the nearer future this should become easier though: #663

9 replies

zacBkh Jul 24, 2025
Author

Is my only solution to switch to i18n routing ?

Yep, that helps you to pre-render pages for different locales.

There are also different ways how you can configure the localePrefix, maybe that's helpful to you!

Thank you!

If I stick to without i18n, but switch from reading the locale from cookies to reading it to database, and manage to cache the database fetch, maybe this can be a workaround or it won't work?
My vision is that the database fetch reading the locale could be done during build phase, hence allowing static rendering.

amannn Jul 24, 2025
Maintainer

If the locale that you're rendering depends on the user, then this will unfortunately not work—no. It would only work if your app only supports a single language, but at that point you could just hardcode the locale anyway.

zacBkh Jul 24, 2025
Author

If the locale that you're rendering depends on the user, then this will unfortunately not work—no. It would only work if your app only supports a single language, but at that point you could just hardcode the locale anyway.

Thank you.
Since this page is public, it does not depend on a user.
It's a bit hacky but if I do a fetch going to my DB that returns let's say en as a default locale (user agnostic) maybe I can get this fetch to happen at build time hence allowing static generation...?
However, problem remains the same since user will not be able to change the locale and interact with cookies then

I don't exactly know how but it would be very efficient to have a way to have a default locale in which the page would be built statically at export and then allow user to change the locale once he visits the page, interacting with cookies!

amannn Jul 24, 2025
Maintainer

Since this page is public, it does not depend on a user.

But can a user change the language of the page? From the currently available information, it seems like you want a setup with i18n routing, static rendering and possibly customize the localePrefix setting. That will give you the most options for static rendering.

You can theoretically also mix the two routing setups.

zacBkh Jul 24, 2025
Author

Since this page is public, it does not depend on a user.

But can a user change the language of the page? From the currently available information, it seems like you want a setup with i18n routing, static rendering and possibly customize the localePrefix setting. That will give you the most options for static rendering.

You can theoretically also mix the two routing setups.

Thanks a lot for your guidance, I am going to have a look at all that.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Next-intl breaking static rendering #1960

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 9 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Next-intl breaking static rendering #1960

Uh oh!

Uh oh!

zacBkh Jul 19, 2025

Replies: 1 comment · 9 replies

Uh oh!

amannn Jul 24, 2025 Maintainer

Uh oh!

zacBkh Jul 24, 2025 Author

Uh oh!

amannn Jul 24, 2025 Maintainer

Uh oh!

zacBkh Jul 24, 2025 Author

Uh oh!

amannn Jul 24, 2025 Maintainer

Uh oh!

zacBkh Jul 24, 2025 Author

zacBkh
Jul 19, 2025

Replies: 1 comment 9 replies

amannn
Jul 24, 2025
Maintainer

zacBkh Jul 24, 2025
Author

amannn Jul 24, 2025
Maintainer

zacBkh Jul 24, 2025
Author

amannn Jul 24, 2025
Maintainer

zacBkh Jul 24, 2025
Author