8000 Add note about NODE_ENV being set automatically · JavaScriptExpert/next.js@0bdcb8d · GitHub
[go: up one dir, main page]

Skip to content

Commit 0bdcb8d

Browse files
committed
Add note about NODE_ENV being set automatically
1 parent 01780fe commit 0bdcb8d

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

readme.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1035,6 +1035,8 @@ Then run `now` and enjoy!
10351035

10361036
Next.js can be deployed to other hosting solutions too. Please have a look at the ['Deployment'](https://github.com/zeit/next.js/wiki/Deployment) section of the wiki.
10371037

1038+
Note: `NODE_ENV` is properly configured by the `next` subcommands, if absent, to maximize performance. if you’re using Next.js [programmatically](#custom-server-and-routing), it’s your responsibility to set `NODE_ENV=production` manually!
1039+
10381040
Note: we recommend putting `.next`, or your custom dist folder (Please have a look at ['Custom Config'](https://github.com/zeit/next.js#custom-configuration). You can set a custom folder in config, `.npmignore`, or `.gitignore`. Otherwise, use `files` or `now.files` to opt-into a whitelist of files you want to deploy (and obviously exclude `.next` or your custom dist folder).
10391041

10401042
## Static HTML export

0 commit comments

Comments
 (0)
0