From 54d70a0f532f39e00720928194876c0d4166c9de Mon Sep 17 00:00:00 2001 From: Paulo Augusto Silva Date: Sat, 1 Oct 2022 21:58:46 -0300 Subject: [PATCH] Docs: Fix misleading `console.log` output example (#41096) The docs have a misleading `console.log` output for the input `process.env` that doesn't display all the variables on edge runtime. The example shows an output of a supposed object with all the environment variables, but it does this when logging a specific variable. ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md) --- docs/api-reference/edge-runtime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/api-reference/edge-runtime.md b/docs/api-reference/edge-runtime.md index 3a6bccc0ae735..3471b5c041672 100644 --- a/docs/api-reference/edge-runtime.md +++ b/docs/api-reference/edge-runtime.md @@ -121,7 +121,7 @@ Running `console.log` on `process.env` **will not** show all your Environment Va console.log(process.env) // { NEXT_RUNTIME: 'edge' } console.log(process.env.TEST_VARIABLE) -// { NEXT_RUNTIME: 'edge', TEST_VARIABLE: 'value' } +// value ``` ## Unsupported APIs