Environment variable management in Remix - Mini Project: Build & Apply

Environment variable management

📖 Scenario: You are building a Remix app that needs to use environment variables to store sensitive data like API keys. This helps keep secrets safe and separate from your code.

🎯 Goal: Create a Remix app setup that reads environment variables correctly and uses them in the app code.

📋 What You'll Learn

Create a .env file with specific environment variables

Load environment variables in Remix using process.env

Use a config file to export environment variables safely

Access environment variables in a Remix route component

💡 Why This Matters

🌍 Real World

Environment variables keep sensitive data like API keys safe and separate from code. This is essential for real-world apps to avoid exposing secrets.

💼 Career

Knowing how to manage environment variables is a key skill for backend and full-stack developers working with modern frameworks like Remix.

1

Create a .env file with variables

Create a .env file in your project root with these exact entries: API_KEY=12345abcde and API_URL=https://api.example.com

Remix

# Create a .env file with API_KEY=12345abcde and API_URL=https://api.example.com

Hint

The .env file should be in the root folder and contain key=value pairs.

2

Create a config file to export env variables

Create a file app/config/env.server.ts that imports process.env and exports constants API_KEY and API_URL from process.env.API_KEY and process.env.API_URL respectively.

Remix

export const API_KEY = process.env.API_KEY;
export const API_URL = process.env.API_URL;
// Your code here

Hint

Use export const to make variables available to other files.

3

Import and use env variables in a route

In app/routes/index.tsx, import API_KEY and API_URL from ../config/env.server. Then create a React component that renders a <div> showing the text API Key: {API_KEY} and API URL: {API_URL}.

Remix

import { API_KEY, API_URL } from '../config/env.server';

export default function Index() {
  return (
    
      {/* Your code here */}
    
  );
}

Hint

Use JSX inside the return statement to display the variables.

4

Add environment variable type safety

In app/config/env.server.ts, add a check that throws an error if API_KEY or API_URL is missing from process.env. Use if (!API_KEY) throw new Error('Missing API_KEY'); and similarly for API_URL.

Remix

const API_KEY = process.env.API_KEY;
const API_URL = process.env.API_URL;

// Add checks for missing env variables below

export { API_KEY, API_URL };

Hint

This ensures your app fails early if environment variables are not set.

Practice

1. What is the main purpose of environment variables in a Remix app?

easy

A. To store secrets and configuration outside the code

B. To style components dynamically

C. To manage user sessions

D. To handle routing between pages

Solution

1. Step 1: Understand environment variables role

   Environment variables hold sensitive data or settings outside the code to keep them secure and flexible.

2. Step 2: Compare options with purpose

   Only To store secrets and configuration outside the code matches this purpose; others relate to styling, sessions, or routing which are unrelated.

3. Final Answer:

   To store secrets and configuration outside the code -> Option A

4. Quick Check:

   Environment variables = secrets/settings outside code [OK]

Hint: Environment variables keep secrets/config outside code [OK]

Common Mistakes:

• Thinking environment variables control styling
• Confusing environment variables with session management
• Assuming environment variables handle routing

2. Which is the correct way to access an environment variable named API_KEY in a Remix loader function?

easy

A. const key = import.meta.env.API_KEY;

B. const key = process.env.API_KEY;

C. const key = env.API_KEY;

D. const key = window.env.API_KEY;

Solution

1. Step 1: Recall Remix environment variable syntax

   In Remix server code, environment variables are accessed via process.env.VARIABLE_NAME.

2. Step 2: Check each option

   const key = process.env.API_KEY; uses process.env.API_KEY, which is correct. Others use invalid or client-only patterns.

3. Final Answer:

   const key = process.env.API_KEY; -> Option B

4. Quick Check:

   Use process.env.VARIABLE_NAME in Remix server code [OK]

Hint: Use process.env.VARIABLE_NAME in Remix server code [OK]

Common Mistakes:

• Using client-side env access like import.meta.env in server code
• Trying to access env variables from window object
• Using undefined variables like env.API_KEY

3. Given this Remix loader code snippet, what will be the value of apiUrl if process.env.API_URL is undefined?

export async function loader() {
  const apiUrl = process.env.API_URL || 'https://default.api.com';
  return { apiUrl };
}

medium

A. Throws an error

B. undefined

C. 'https://default.api.com'

D. null

Solution

1. Step 1: Understand the || operator behavior

   If process.env.API_URL is undefined (falsy), the expression returns the right side string.

2. Step 2: Apply to given code

   Since process.env.API_URL is undefined, apiUrl becomes 'https://default.api.com'.

3. Final Answer:

   'https://default.api.com' -> Option C

4. Quick Check:

   Falsy env var uses default string [OK]

Hint: Use || to provide default if env var is missing [OK]

Common Mistakes:

• Expecting undefined instead of default string
• Thinking it throws an error if env var missing
• Confusing null with undefined

4. Identify the error in this Remix code snippet that tries to expose a secret API key to the client:

export function loader() {
  return { apiKey: process.env.SECRET_API_KEY };
}

export default function Component() {
  const { apiKey } = useLoaderData();
  return <div>API Key: {apiKey}</div>;
}

medium

A. Missing async keyword in loader function

B. process.env.SECRET_API_KEY is undefined in loader

C. useLoaderData cannot access loader return values

D. Exposing SECRET_API_KEY to client is a security risk

Solution

1. Step 1: Understand environment variable exposure

   Secrets like API keys should never be sent to the client because it exposes sensitive data.

2. Step 2: Analyze the code behavior

   The loader returns the secret key, which the component renders, exposing it in the browser.

3. Final Answer:

   Exposing SECRET_API_KEY to client is a security risk -> Option D

4. Quick Check:

   Never send secrets to client [OK]

Hint: Never send secret env vars to client components [OK]

Common Mistakes:

• Thinking loader cannot access env vars
• Believing useLoaderData can't access loader data
• Assuming async is required for all loaders

5. You want to safely use a public API key in your Remix app's client code and keep a secret key only on the server. Which approach correctly manages environment variables?

hard

A. Prefix public keys with PUBLIC_ and access them in client code; keep secrets without prefix and access only in server code

B. Store all keys in process.env and access them directly in client code

C. Put all keys in a JSON file and import it in both client and server code

D. Use window.env to store keys and access anywhere

Solution

1. Step 1: Understand Remix environment variable conventions

   Remix exposes environment variables prefixed with PUBLIC_ to client code safely; secrets remain server-only.

2. Step 2: Evaluate options for security and access

   Prefix public keys with PUBLIC_ and access them in client code; keep secrets without prefix and access only in server code follows this pattern, separating public and secret keys correctly. Others expose secrets or use insecure methods.

3. Final Answer:

   Prefix public keys with PUBLIC_ and access them in client code; keep secrets without prefix and access only in server code -> Option A

4. Quick Check:

   Use PUBLIC_ prefix for client env vars [OK]

Hint: Prefix public env vars with PUBLIC_ for safe client use [OK]

Common Mistakes:

• Exposing all keys to client without prefix
• Storing secrets in JSON files accessible to client
• Using window.env which is not standard