Environment configuration in Node.js - Mini Project: Build & Apply

Environment Configuration in Node.js

📖 Scenario: You are building a simple Node.js application that needs to connect to a database. To keep your database connection details safe and flexible, you will use environment variables.

🎯 Goal: Create a Node.js script that reads database connection details from environment variables and logs a connection message using those details.

📋 What You'll Learn

Create environment variables for database host, user, and password

Use a configuration object to hold these variables

Write a function that uses the configuration to simulate a database connection message

Log the connection message using the configuration values

💡 Why This Matters

🌍 Real World

Environment variables keep sensitive data like passwords out of your code and allow easy changes without editing code.

💼 Career

Understanding environment configuration is essential for backend developers to build secure and flexible applications.

1

Set up environment variables

Create three environment variables named DB_HOST, DB_USER, and DB_PASS with the exact values localhost, admin, and secret123 respectively. Use process.env to access these variables in your Node.js script.

Node.js

// Access environment variables DB_HOST, DB_USER, and DB_PASS
// Your code here

Hint

Use process.env.VARIABLE_NAME to read environment variables in Node.js.

2

Create a configuration object

Create a constant object named dbConfig that holds the properties host, user, and password using the variables DB_HOST, DB_USER, and DB_PASS.

Node.js

const DB_HOST = process.env.DB_HOST;
const DB_USER = process.env.DB_USER;
const DB_PASS = process.env.DB_PASS;

// Create dbConfig object here
// Your code here

Hint

Create an object with keys host, user, and password assigned to the environment variables.

3

Write a function to simulate connection

Write a function named connectToDatabase that takes the dbConfig object as a parameter and returns a string: Connected to database at HOST with user USER, replacing HOST and USER with the corresponding values from dbConfig.

Node.js

const DB_HOST = process.env.DB_HOST;
const DB_USER = process.env.DB_USER;
const DB_PASS = process.env.DB_PASS;

const dbConfig = {
  host: DB_HOST,
  user: DB_USER,
  password: DB_PASS
};

// Write connectToDatabase function here
// Your code here

Hint

Use a template string to include config.host and config.user in the returned message.

4

Log the connection message

Call the connectToDatabase function with dbConfig and assign the result to a constant named connectionMessage. Then, log connectionMessage to the console.

Node.js

const DB_HOST = process.env.DB_HOST;
const DB_USER = process.env.DB_USER;
const DB_PASS = process.env.DB_PASS;

const dbConfig = {
  host: DB_HOST,
  user: DB_USER,
  password: DB_PASS
};

function connectToDatabase(config) {
  return `Connected to database at ${config.host} with user ${config.user}`;
}

// Call function and log the message
// Your code here

Hint

Assign the function call result to connectionMessage and use console.log to display 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