chore(docs): explain NODE_ENV environment variable
#52003
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ijjk
reviewed
Jun 29, 2023
| @@ -168,3 +168,4 @@ For example, if `NODE_ENV` is `development` and you define a variable in both `. | |||
| ## Good to know | |||
|
|
|||
| - If you are using a [`/src` directory](/docs/app/building-your-application/configuring/src-directory), `.env.*` files should remain in the root of your project. | |||
| - The environment variable `NODE_ENV` is automatically assigned to `development` when running `next dev`. All other commands automatically assign `NODE_ENV` to `production`. | |||
There was a problem hiding this comment.
We don't override test if set x-ref:
next.js/packages/next/src/bin/next.ts
Line 84 in e104316
There was a problem hiding this comment.
Looks like we don't override at all. We just have defaults.
ijjk
approved these changes
Jun 29, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR documents the
NODE_ENVenvironment variable behavior.This feature was originally added in 152c2c2 which was released in
next@5.See the current source code here:
next.js/packages/next/src/bin/next.ts
Line 82 in e3e76a4