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

Clarify that publicRuntimeConfig and serverRuntimeConfig do not work with Output File Tracing #43443

Merged
merged 4 commits into from Nov 30, 2022
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/api-reference/next.config.js/runtime-configuration.md
Expand Up @@ -6,6 +6,8 @@ description: Add client and server runtime configuration to your Next.js app.

> Generally you'll want to use [build-time environment variables](/docs/basic-features/environment-variables.md) to provide your configuration. The reason for this is that runtime configuration adds rendering / initialization overhead and is incompatible with [Automatic Static Optimization](/docs/advanced-features/automatic-static-optimization.md).
> This feature is [now considered legacy and does not work with Output File Tracing](/docs/advanced-features/output-file-tracing#automatically-copying-traced-files).
To add runtime configuration to your app open `next.config.js` and add the `publicRuntimeConfig` and `serverRuntimeConfig` configs:
delbaoliveira marked this conversation as resolved.
Show resolved Hide resolved

```js
Expand Down