rsnext/errors/env-key-not-allowed.md

# The key "<your key>" under "env" in next.config.js is not allowed.

#### Why This Error Occurred

Next.js configures internal variables for replacement itself. `NEXT_RUNTIME` along with variables starting with `__` or `NODE_` are currently internal, for this reason they are not allowed as values for `env` in `next.config.js`

#### Possible Ways to Fix It

Rename the specified key so that it does not start with `__` or `NODE_`, or pick other another name for `NEXT_RUNTIME`.
Block Certain Env Keys That Are Used Internally (#6260) Closes: #6244 This will block the following keys: ``` NODE_.+ __.+ ``` There doesn't seem to be a way to simulate a failed build or else I'd add tests for it. 2019-02-15 17:49:40 +01:00			`# The key "<your key>" under "env" in next.config.js is not allowed.`

			`#### Why This Error Occurred`

Add process env NEXT_RUNTIME (#36383) * To help determine the current running environment is in server nodejs / edge runtime * Remove usage of `process.browser` 2022-04-26 19:54:28 +02:00			Next.js configures internal variables for replacement itself. `NEXT_RUNTIME` along with variables starting with `__` or `NODE_` are currently internal, for this reason they are not allowed as values for `env` in `next.config.js`
Block Certain Env Keys That Are Used Internally (#6260) Closes: #6244 This will block the following keys: ``` NODE_.+ __.+ ``` There doesn't seem to be a way to simulate a failed build or else I'd add tests for it. 2019-02-15 17:49:40 +01:00
			`#### Possible Ways to Fix It`

Add process env NEXT_RUNTIME (#36383) * To help determine the current running environment is in server nodejs / edge runtime * Remove usage of `process.browser` 2022-04-26 19:54:28 +02:00			Rename the specified key so that it does not start with `__` or `NODE_`, or pick other another name for `NEXT_RUNTIME`.