From abf6e74e8d79c096f2c035d4187fbae86c1b4ac0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sigur=C3=B0ur=20Gunnar=20Nj=C3=A1lsson?= Date: Wed, 5 Aug 2020 16:11:01 +0000 Subject: [PATCH] Remove outdated docs on serverless builds and runtime configs (#15907) Fixes https://github.com/vercel/next.js/issues/15906 This should solve https://github.com/vercel/next.js/issues/15906. It simply removes a block that states runtime configuration for serverless builds are not supported. --- docs/api-reference/next.config.js/runtime-configuration.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/api-reference/next.config.js/runtime-configuration.md b/docs/api-reference/next.config.js/runtime-configuration.md index 4a4a2a5ace6e..b52e3e889856 100644 --- a/docs/api-reference/next.config.js/runtime-configuration.md +++ b/docs/api-reference/next.config.js/runtime-configuration.md @@ -6,8 +6,6 @@ description: Add client and server runtime configuration to your Next.js app. > Generally you'll want to use [build-time environment variables](/docs/api-reference/next.config.js/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). -> Runtime configuration is not available when using the [`serverless` target](/docs/api-reference/next.config.js/build-target.md#serverless-target). - To add runtime configuration to your app open `next.config.js` and add the `publicRuntimeConfig` and `serverRuntimeConfig` configs: ```js