Environment configuration in Node.js - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the purpose of the .env file in a Node.js project?

Choose the best explanation for why developers use a .env file in Node.js projects.

A To define the structure of the database used by the application.

B To write the main application logic and server code.

C To list all installed Node.js packages and their versions.

D To store environment-specific configuration variables securely outside the codebase.

💡 Hint

Think about how you keep secret keys or settings separate from your code.

The .env file holds environment variables like API keys or database URLs. This keeps sensitive info out of the code and allows easy changes per environment.

❓ component_behavior

intermediate

What will this Node.js code output when using dotenv?

Given the .env file contains: API_KEY=12345 What does the following code print?

Node.js

import dotenv from 'dotenv';
dotenv.config();
console.log(process.env.API_KEY);

A Error: dotenv not found

B undefined

C 12345

D null

💡 Hint

dotenv loads variables into process.env

dotenv.config() loads variables from .env into process.env. So process.env.API_KEY will be '12345'.

📝 Syntax

advanced

Which option correctly loads environment variables using ES modules in Node.js?

Select the code snippet that correctly imports and configures dotenv in a Node.js ES module.

A

import { config } from 'dotenv';
config();

B

const dotenv = require('dotenv');
dotenv.config();

C require('dotenv').config();

D

import dotenv from 'dotenv';
dotenv.config();

💡 Hint

ES modules use import syntax, not require.

In ES modules, you can import the named export 'config' and call it directly. Option A uses correct ES module syntax.

🔧 Debug

advanced

Why does process.env.MY_VAR return undefined in this Node.js app?

Given .env contains MY_VAR=hello And code is: import dotenv from 'dotenv'; console.log(process.env.MY_VAR); dotenv.config(); Why is the output undefined?

Node.js

import dotenv from 'dotenv';
console.log(process.env.MY_VAR);
dotenv.config();

A process.env variables are only available in CommonJS modules.

B dotenv.config() must be called before accessing process.env variables.

C The .env file is missing from the project root.

D MY_VAR is not a valid environment variable name.

💡 Hint

Think about when dotenv loads the variables.

dotenv.config() loads variables into process.env. If you access process.env before calling config(), variables are not loaded yet.

❓ state_output

expert

What is the output of this Node.js code with multiple dotenv.config calls?

Assuming .env contains VAR=first and .env.local contains VAR=second, What does this code print?

Node.js

import dotenv from 'dotenv';
dotenv.config({ path: '.env' });
dotenv.config({ path: '.env.local' });
console.log(process.env.VAR);

A first

B Error: Multiple dotenv.config calls not allowed

C undefined

D second

💡 Hint

dotenv.config() does not override existing environment variables by default.

dotenv.config() loads variables into process.env but does not overwrite existing keys by default (override: false). The first call sets VAR='first'. The second call finds VAR already set and skips it.

Practice

1. What is the main purpose of using environment configuration in a Node.js application?

easy

A. To make the application run faster by hardcoding values

B. To write all configuration directly inside the main JavaScript files

C. To separate settings like API keys and ports from the code for flexibility and security

D. To avoid using any external packages or files

Solution

1. Step 1: Understand environment configuration purpose

   Environment configuration helps keep settings like API keys, database URLs, and ports separate from the code.

2. Step 2: Recognize benefits

   This separation allows changing settings without touching code and keeps secrets safe.

3. Final Answer:

   To separate settings like API keys and ports from the code for flexibility and security -> Option C

4. Quick Check:

   Environment configuration = separate settings [OK]

Hint: Think: config outside code for safety and flexibility [OK]

Common Mistakes:

• Hardcoding secrets inside code
• Ignoring security by mixing config and code
• Not using environment variables

2. Which of the following is the correct way to load environment variables from a .env file using the dotenv package in Node.js?

easy

A. require('dotenv').config()

B. import dotenv from 'dotenv'; dotenv.load()

C. require('dotenv').loadEnv()

D. import dotenv from 'dotenv'; dotenv.setup()

Solution

1. Step 1: Recall dotenv usage

   The standard way to load environment variables is calling require('dotenv').config() at the start of your app.

2. Step 2: Check other options

   Options A, B, and D use incorrect method names or syntax not supported by dotenv.

3. Final Answer:

   require('dotenv').config() -> Option A

4. Quick Check:

   dotenv load method = config() [OK]

Hint: Remember: dotenv uses config() to load variables [OK]

Common Mistakes:

• Using wrong method names like load() or setup()
• Mixing import and require incorrectly
• Forgetting to call config()

3. Given the following code snippet and a .env file with PORT=4000, what will be the output?

require('dotenv').config();
console.log(process.env.PORT || 3000);

medium

A. 4000

B. undefined

C. Error: PORT not defined

D. 3000

Solution

1. Step 1: dotenv loads .env variables into process.env

   The call to require('dotenv').config() loads PORT=4000 into process.env.PORT.

2. Step 2: Evaluate console.log expression

   The expression process.env.PORT || 3000 uses the loaded value 4000, so it prints 4000.

3. Final Answer:

   4000 -> Option A

4. Quick Check:

   Loaded PORT = 4000 [OK]

Hint: Loaded env vars override defaults [OK]

Common Mistakes:

• Assuming default 3000 prints even if PORT is set
• Thinking process.env.PORT is undefined
• Expecting an error if .env exists

4. What is the error in this Node.js code that tries to use environment variables?

import dotenv from 'dotenv';
dotenv.config;
console.log(process.env.DB_HOST);

medium

A. dotenv package not imported correctly

B. Missing parentheses after config method call

C. process.env.DB_HOST is undefined by default

D. Cannot use import syntax in Node.js

Solution

1. Step 1: Check dotenv usage

   The code calls dotenv.config without parentheses, so the config function is not executed.

2. Step 2: Effect of missing parentheses

   Without calling config(), environment variables from .env are not loaded, so process.env.DB_HOST may be undefined.

3. Final Answer:

   Missing parentheses after config method call -> Option B

4. Quick Check:

   Call config() with () to load env [OK]

Hint: Always call config() with parentheses [OK]

Common Mistakes:

• Forgetting () after config
• Assuming import syntax always fails
• Ignoring that process.env can be empty

5. You want to safely use an API key in your Node.js app without exposing it in your code. Which approach correctly applies environment configuration best practices?

hard

A. Write the API key in a JSON file and require it in your code

B. Hardcode the API key directly in your main JavaScript file for easy access

C. Push the API key to your public GitHub repository for backup

D. Store the API key in a .env file, load it with dotenv, and access it via process.env.API_KEY

Solution

1. Step 1: Identify secure storage method

   Storing secrets like API keys in a .env file keeps them out of code and version control.

2. Step 2: Use dotenv to load and access keys

   Using dotenv loads the key into process.env, which the app can safely use.

3. Final Answer:

   Store the API key in a .env file, load it with dotenv, and access it via process.env.API_KEY -> Option D

4. Quick Check:

   Secrets in .env, not code [OK]

Hint: Keep secrets in .env, never in code [OK]

Common Mistakes:

• Hardcoding secrets in code files
• Committing secrets to public repos
• Using insecure files for secrets