dynamic = "force-static" does not apply when used on a page file

[arrofirezasatria]

When using export const dynamic = 'force-static' in a Next.js page (e.g., inside a page.tsx or page.js file within the app directory), the page does not behave as expected. It does not enforce static generation and still behaves as if it's dynamic.

Reproduction :

1. Create a new route under app/page.tsx.

2. Add the following:

export const dynamic = 'force-static';

export default function Page() {
  console.log("Running on server");
  return <div>Hello from static</div>;
}

3. Run next build && next start or next dev

Expected Behaviour

The page should be statically generated at build time (similar to using getStaticProps in the old pages router) and not include any dynamic logic or server rendering at runtime.

Actual Behaviour

redirect to 404 pages and have an error message below
Unable to find `next-intl` locale because the middleware didn't run on this request and no `locale` was returned in `getRequestConfig`. See https://next-intl.dev/docs/routing/middleware#unable-to-find-locale. The `notFound()` function will be called as a result.

[stepan662]

Hi, I didn't manage to replicate your issue exactly. Could you provide a more detailed way to reproduce (e.g. exact path to newly created route)?

I think in order for next-intl to work, you need to have all your routes in the [locale] folder, so that might be the problem. I've tested this and everything seems to work as expected.

[arrofirezasatria]

Hi, Yes the newly route is is under [locale], Im not sure wether this is next-intl issue or tolgee issue.

[stepan662]

Ah, ok. Now I was able to replicate, not sure what I was doing wrong before...

I think it's a behaviour of next-intl, they have a docs page about this:
https://next-intl.dev/docs/getting-started/app-router/with-i18n-routing#static-rendering