Environment-based configuration in Express - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to load environment variables from a .env file.

Express

require('[1]').config();

Drag options to blanks, or click blank then click option'

Aconfig

Bexpress

Cdotenv

Denv

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'express' instead of 'dotenv' to load environment variables.

Forgetting to call the config() method after requiring the package.

The dotenv package loads environment variables from a .env file into process.env.

2fill in blank

medium

Complete the code to access the PORT environment variable with a fallback value.

Express

const port = process.env.[1] || 3000;

Drag options to blanks, or click blank then click option'

AHOST

BPORT

CNODE_ENV

DDATABASE_URL

Attempts:

3 left

💡 Hint

Common Mistakes

Using HOST instead of PORT for the server port.

Not providing a fallback value.

process.env.PORT accesses the port number set in environment variables. The fallback 3000 is used if PORT is not set.

3fill in blank

hard

Fix the error in the code to correctly use environment variables in Express.

Express

app.listen([1], () => {
  console.log(`Server running on port ${port}`);
});

Drag options to blanks, or click blank then click option'

Aport

Bprocess.env.PORT

C3000

DPORT

Attempts:

3 left

💡 Hint

Common Mistakes

Passing process.env.PORT directly without fallback.

Passing the string 'PORT' instead of a number.

The variable port holds the port number with fallback. Using port here ensures the server listens on the correct port.

4fill in blank

hard

Fill both blanks to set a default environment and log it.

Express

const env = process.env.[1] || '[2]';
console.log(`Running in ${env} mode`);

Drag options to blanks, or click blank then click option'

ANODE_ENV

Bproduction

Cdevelopment

DPORT

Attempts:

3 left

💡 Hint

Common Mistakes

Using PORT instead of NODE_ENV for environment mode.

Setting production as default instead of development.

NODE_ENV is the standard environment variable for the app mode. The default is usually set to development for local testing.

5fill in blank

hard

Fill all three blanks to create a config object using environment variables.

Express

const config = {
  host: process.env.[1] || 'localhost',
  port: process.env.[2] || 5432,
  user: process.env.[3] || 'admin'
};

Drag options to blanks, or click blank then click option'

ADB_HOST

BDB_PORT

CDB_USER

DDATABASE_URL

Attempts:

3 left

💡 Hint

Common Mistakes

Using DATABASE_URL instead of separate variables for host, port, and user.

Mixing up the order of variables.

This config object uses environment variables for database connection details with sensible defaults.

Practice

1. What is the main purpose of using environment-based configuration in an Express app?

easy

A. To change app settings without modifying the code

B. To write all configuration directly inside the code

C. To make the app run only on one specific machine

D. To avoid using any external files or variables

Solution

1. Step 1: Understand environment-based configuration

   It allows changing settings like ports or database URLs without changing the app code.

2. Step 2: Compare options

   Only To change app settings without modifying the code describes this purpose correctly; others contradict the idea of flexible configuration.

3. Final Answer:

   To change app settings without modifying the code -> Option A

4. Quick Check:

   Environment config = change settings without code [OK]

Hint: Think: config changes without code edits [OK]

Common Mistakes:

• Confusing environment config with hardcoded settings
• Thinking environment config restricts app to one machine
• Assuming environment config means no external variables

2. Which of the following is the correct way to access an environment variable named PORT in an Express app?

easy

A. const port = process.env.PORT;

B. const port = env.PORT;

C. const port = process.PORT;

D. const port = process.env['port'];

Solution

1. Step 1: Recall how to access environment variables in Node.js

   Use process.env.VARIABLE_NAME to get environment variables.

2. Step 2: Check each option

   const port = process.env.PORT; uses the correct syntax. const port = env.PORT; misses process. const port = process.PORT; uses wrong property. const port = process.env['port']; uses lowercase key which is case-sensitive and usually environment variables are uppercase.

3. Final Answer:

   const port = process.env.PORT; -> Option A

4. Quick Check:

   Use process.env.VAR to access env variables [OK]

Hint: Always use process.env.VAR to get env variables [OK]

Common Mistakes:

• Omitting 'process' before 'env'
• Using wrong casing for environment variable names
• Accessing environment variables as properties of process

3. Consider this Express code snippet:

const port = process.env.PORT || 3000;
app.listen(port, () => {
  console.log(`Server running on port ${port}`);
});

If the environment variable PORT is set to 5000, what will be printed when the server starts?

medium

A. Server running on port process.env.PORT

B. Server running on port 3000

C. Server running on port undefined

D. Server running on port 5000

Solution

1. Step 1: Understand the fallback logic

   The code uses process.env.PORT || 3000, so if PORT is set, it uses that; otherwise, 3000.

2. Step 2: Apply given environment variable

   Since PORT is set to 5000, the server listens on port 5000 and prints that.

3. Final Answer:

   Server running on port 5000 -> Option D

4. Quick Check:

   Env var set? Use it; else default [OK]

Hint: If env var exists, use it; else fallback [OK]

Common Mistakes:

• Ignoring the environment variable and using default
• Printing the variable name instead of its value
• Assuming undefined if environment variable exists

4. You wrote this code to read a secret key:

const secret = process.env.SECRET_KEY;
console.log(secret.length);

But when you run the app, it crashes with TypeError: Cannot read property 'length' of undefined. What is the likely cause?

medium

A. You must use process.SECRET_KEY instead of process.env.SECRET_KEY

B. The secret key is empty string, so length is undefined

C. The environment variable SECRET_KEY is not set

D. You need to convert secret to a string before accessing length

Solution

1. Step 1: Analyze the error message

   The error says length is accessed on undefined, meaning secret is undefined.

2. Step 2: Check environment variable usage

   If SECRET_KEY is not set in environment, process.env.SECRET_KEY is undefined, causing the error.

3. Final Answer:

   The environment variable SECRET_KEY is not set -> Option C

4. Quick Check:

   Undefined env var causes undefined value [OK]

Hint: Check if env variable is set before using it [OK]

Common Mistakes:

• Assuming env variable is always defined
• Using wrong property to access env variables
• Not handling undefined values before property access

5. You want to configure your Express app to use different database URLs for development and production environments. Which approach correctly uses environment variables and safe defaults?

hard

A. const dbUrl = process.env.DB_URL && 'mongodb://localhost/devdb';

B. const dbUrl = process.env.DB_URL || 'mongodb://localhost/devdb';

C. const dbUrl = 'mongodb://localhost/devdb'; if (process.env.NODE_ENV === 'production') dbUrl = process.env.DB_URL;

D. const dbUrl = process.env.DB_URL ? 'mongodb://localhost/devdb' : process.env.DB_URL;

Solution

1. Step 1: Understand environment-based config with fallback

   Use environment variable if set; otherwise, use a safe default URL.

2. Step 2: Evaluate each option

   const dbUrl = process.env.DB_URL || 'mongodb://localhost/devdb'; correctly uses process.env.DB_URL || default. const dbUrl = 'mongodb://localhost/devdb'; if (process.env.NODE_ENV === 'production') dbUrl = process.env.DB_URL; tries to reassign a const variable (error). const dbUrl = process.env.DB_URL && 'mongodb://localhost/devdb'; uses && which returns false if DB_URL is missing. const dbUrl = process.env.DB_URL ? 'mongodb://localhost/devdb' : process.env.DB_URL; reverses the condition, causing wrong assignment.

3. Final Answer:

   const dbUrl = process.env.DB_URL || 'mongodb://localhost/devdb'; -> Option B

4. Quick Check:

   Use env var or fallback default [OK]

Hint: Use env var OR fallback default with || [OK]

Common Mistakes:

• Reassigning const variables
• Using && instead of || for fallback
• Swapping condition logic causing wrong URL