What does the Node.js `--env-file` flag do, and does it replace dotenv?

Q: What does the Node.js `--env-file` flag do, and does it replace dotenv?

**Target Audience:** Engineers preparing for Node.js backend interviews — assumes basic `process.env` familiarity. **Difficulty:** Easy > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Everything below was **executed against Node v24.19.0** — the raw output is pasted in section 3. ## 1. Why This Even Matters — A Story First For years, every Node tutorial opened the same way: npm install dotenv , then require("dotenv").config() at the very top of the entry file. A package existed to do something that sounds almost too small to need one — read a text file and copy its lines into an object. It became a package because Node genuinely had no other way to do it. That changed, and a lot of projects have not noticed yet. ## 2. The Core Idea 📌 **Interview term: --env-file ** — a command-line flag, stable since Node 20.6, that reads a file of KEY=value lines and l

The problem

Question presented to candidate: "Every Node project seems to install dotenv. Do you still need it?"

What a strong answer should cover:

Since Node 20.6, node --env-file=.env your-script.js loads key-value pairs from a file straight into process.env before your code runs — no package required.
It is a CLI flag, not an API you call from inside your code — so it must be present on every command that starts the process (node, npm start, your Docker CMD), including test runners.
--env-file-if-exists is the forgiving variant: it does not error when the file is missing, which matters for environments (CI, a fresh clone) where a .env may not exist.
It supports basic KEY=value syntax and # comments; it does not run shell expansion or nested variable interpolation the way some dotenv-adjacent tools do.
Existing process.env values (already set by the shell or the orchestrator) are not overwritten by the file — the file only fills in what is missing.
It does not replace dotenv's whole ecosystem overnight: multi-file layering (.env.local, .env.production), variable expansion, and framework auto-loading are still dotenv-shaped conveniences some projects want.

Clarifying questions expected:

"Which Node version is this running on in production?" — anything older than 20.6 needs the package.
"Does anything rely on interpolated variables inside the .env file?" — that is the feature gap.

Code / implementation expected: Optional. Showing the flag and process.env reading it is enough.

env-file
dotenv
configuration
cli-flags

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for Node.js backend interviews — assumes basic process.env familiarity. Difficulty: Easy

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Everything below was executed against Node v24.19.0 — the raw output is pasted in section 3.

1. Why This Even Matters — A Story First

For years, every Node tutorial opened the same way: npm install dotenv, then require("dotenv").config() at the very top of the entry file. A package existed to do something that sounds almost too small to need one — read a text file and copy its lines into an object.

It became a package because Node genuinely had no other way to do it. That changed, and a lot of projects have not noticed yet.

2. The Core Idea

📌 Interview term: --env-file — a command-line flag, stable since Node 20.6, that re

The solution is hidden so you can try first

6 min read · 9 sections

Read the code

Reading a value loaded purely by the flag — no package installed

$ cat .env
GREETING=hello

$ node --env-file=.env -e "console.log(process.env.GREETING)"
hello

# The forgiving variant does nothing (no error) when the file is absent:
$ node --env-file-if-exists=.env.missing -e "console.log('still running')"
still running

Discussion

Other approaches, follow-ups and how it went in real interviews.

Sign in to join the discussion.

No comments yet. Share how you would answer it.

The solution is hidden so you can try first

Keep your momentum going.