NextJS static rendering does not work when working with next-int

Question

According to next-intel documentation, we can use setRequestLocale to enable static rendering, but it's not working. I'm trying to apply static rendering to all pages under [locale] path, but when I run npm run build, I see all of them are dynamic (server-rendered on demand):

import { NextIntlClientProvider } from "next-intl";
import { getMessages, setRequestLocale } from "next-intl/server";
import { routing } from "@/i18n/routing";
import Header from "./header/Header";
import "./globals.css";


export default async function LocaleLayout({ children, params }) {
  // Ensure that the incoming `locale` is valid
  const { locale } = await params;
  if (!routing.locales.includes(locale)) {
    notFound();
  }

  // Enable static rendering
  setRequestLocale(locale);

  const messages = await getMessages();

  return (
    <html lang={locale}>
      <body className={`${rubik.className} sans-serif`}>
        <NextIntlClientProvider messages={messages}>
          <Header />
          {children}
        </NextIntlClientProvider>
      </body>
    </html>
  );
}

Morgana Freeman · Accepted Answer · 2024-12-23 12:27:13Z

1

I need to add generateStaticParams function for locales:

export function generateStaticParams() {
  return routing.locales.map((locale) => ({ locale }));
}

export default async function LocaleLayout({ children, params }) {
...
}

now all my component inside [locale] path are SSG (prerendered as static HTML) which have the same result as static, if i'm not wrong, extremely fast and effective for SEO

answered Dec 23, 2024 at 12:27

Morgana Freeman

1391 silver badge11 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

NextJS static rendering does not work when working with next-int

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related