From 60239c44480789983c3d7a51e020809ca2dbb454 Mon Sep 17 00:00:00 2001 From: Augustin Mauroy Date: Mon, 16 Dec 2024 17:45:50 +0100 Subject: [PATCH] rephrase sentences Co-authored-by: Ruy Adorno Signed-off-by: Augustin Mauroy --- .../how-to-read-environment-variables-from-nodejs.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/apps/site/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md b/apps/site/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md index e30a18b495d8b..d4d84c6c2e04d 100644 --- a/apps/site/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md +++ b/apps/site/pages/en/learn/command-line/how-to-read-environment-variables-from-nodejs.md @@ -58,8 +58,8 @@ node --env-file=.env --env-file=.development.env app.js > Note: if the same variable is defined in the environment and in the file, the value from the environment takes precedence. -But there may be a problem: if the file doesn't exist, it will return an error. -To avoid this, you can use the `--env-file-if-exists` flag. +In case you want to optionally read from a `.env` file, it's possible to avoid +throwing an error if the file is missing using the `--env-file-if-exists` flag. ```bash node --env-file-if-exists=.env app.js