Environment configuration in Node.js - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is environment configuration in Node.js?

Environment configuration means setting up variables and settings that control how your Node.js app runs in different places, like development or production.

beginner

Why use environment variables instead of hardcoding values?

Environment variables keep sensitive info like passwords safe and let you change settings without changing code, making your app flexible and secure.

beginner

What file is commonly used to store environment variables locally in Node.js projects?

The .env file stores environment variables locally. It is simple text with key=value pairs and should not be shared publicly.

beginner

How do you access an environment variable named PORT in Node.js?

Use process.env.PORT to get the value of the PORT environment variable in your Node.js code.

beginner

What is the purpose of the dotenv package in Node.js?

The dotenv package loads variables from a .env file into process.env so your app can use them easily during development.

Which of these is the correct way to access an environment variable named API_KEY in Node.js?

A process.env['api_key']

B process.API_KEY

C env.API_KEY

D process.env.API_KEY

Environment variables are accessed using process.env.VARIABLE_NAME with exact case.

What file should you add to .gitignore to keep environment variables private?

A config.js

B .env

C package.json

D README.md

The .env file contains sensitive info and should not be pushed to public repositories.

What does the dotenv package do in a Node.js project?

A Loads variables from .env into process.env

B Compiles JavaScript code

C Manages database connections

D Runs tests automatically

Dotenv reads .env files and sets environment variables for your app.

Why is it better to use environment variables for configuration?

A They automatically fix bugs

B They make code run faster

C They keep sensitive data out of code and allow easy changes

D They reduce file size

Environment variables separate config from code, improving security and flexibility.

Which command installs the dotenv package in a Node.js project?

A npm install dotenv

B npm install express

C node dotenv

D npm start dotenv

Use npm install dotenv to add the dotenv package to your project.

Explain how environment variables help manage different settings for development and production in Node.js.

Think about how you might run your app on your computer vs on a server.

Describe the steps to set up environment configuration using a .env file and the dotenv package in a Node.js project.

Imagine you want to keep your secret keys safe and easy to change.

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