Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NextIntlClientProvider unexpectedly reads from headers #631

Closed
amannn opened this issue Nov 15, 2023 Discussed in #628 · 0 comments · Fixed by #633
Closed

NextIntlClientProvider unexpectedly reads from headers #631

amannn opened this issue Nov 15, 2023 Discussed in #628 · 0 comments · Fixed by #633
Labels
bug Something isn't working

Comments

@amannn
Copy link
Owner

amannn commented Nov 15, 2023

Discussed in #628

Originally posted by kjxbyz November 15, 2023

Description

StaticGenBailoutError: Page with `dynamic = "error"` couldn't be rendered statically because it used `headers`. See more info here: https://nextjs.org/docs/app/building-your-application/rendering/static-and-dynamic#dynamic-rendering
--
00:51:10.529 | at staticGenerationBailout (/vercel/path0/app/.next/server/chunks/570.js:1:81342)
00:51:10.529 | at headers (/vercel/path0/app/.next/server/chunks/41.js:13:49131)
00:51:10.529 | at /vercel/path0/app/.next/server/chunks/41.js:13:44243
00:51:10.529 | at /vercel/path0/node_modules/.pnpm/next@14.0.1_@babel+core@7.23.2_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:108:5119
00:51:10.529 | at s (/vercel/path0/app/.next/server/chunks/41.js:13:44967)
00:51:10.529 | at e (/vercel/path0/app/.next/server/chunks/41.js:13:45059)
00:51:10.529 | at m (/vercel/path0/app/.next/server/chunks/41.js:13:46804)
00:51:10.529 | at em (/vercel/path0/node_modules/.pnpm/next@14.0.1_@babel+core@7.23.2_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:76:10452)
00:51:10.529 | at /vercel/path0/node_modules/.pnpm/next@14.0.1_@babel+core@7.23.2_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:76:22148
00:51:10.530 | at Object.toJSON (/vercel/path0/node_modules/.pnpm/next@14.0.1_@babel+core@7.23.2_@opentelemetry+api@1.6.0_react-dom@18.2.0_react@18.2.0/node_modules/next/dist/compiled/next-server/app-page.runtime.prod.js:76:25726) {
00:51:10.530 | code: 'NEXT_STATIC_GEN_BAILOUT'

Mandatory reproduction URL (CodeSandbox or GitHub repository)

cyf/faforever-tauri#72

Reproduction description

Steps to reproduce:

  1. git clone https://github.com/cyf/faforever-next
  2. git fetch
  3. git checkout origin/renovate/next-intl-3.x -b renovate/next-intl-3.x
  4. pnpm i
  5. pnpm build:app

Expected behaviour

When output is export, the build is normal

@amannn amannn added bug Something isn't working unconfirmed Needs triage. and removed unconfirmed Needs triage. labels Nov 15, 2023
amannn added a commit that referenced this issue Nov 15, 2023
…ese options have been provided to `NextIntlClientProvider` (#633)

Fixes #631 

See corresponding section in the release notes: [Changes to
`NextIntlClientProvider`](https://next-intl-docs.vercel.app/blog/next-intl-3-0#changes-to-nextintlclientprovider)
(once this PR is merged)
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
1 participant