Environment variable management in Remix - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of environment variables in Remix?

Environment variables store configuration values outside the code. They help keep secrets safe and allow different settings for development, testing, and production.

beginner

How do you access environment variables in a Remix loader function?

You can access environment variables using process.env.VARIABLE_NAME inside loader functions because they run on the server.

intermediate

Why should you prefix environment variables with PUBLIC_ in Remix apps?

Only variables prefixed with PUBLIC_ are exposed to the client-side code. This protects other variables from being leaked to the browser.

beginner

Where do you define environment variables for Remix during local development?

You define them in a .env file at the root of your project. Remix loads these variables automatically when you run the app locally.

intermediate

How can you safely use secret keys in Remix without exposing them to the client?

Keep secret keys in environment variables without the PUBLIC_ prefix. Use them only in server code like loaders or actions, never in client code.

Which environment variable prefix exposes the variable to client-side code in Remix?

A APP_

B REACT_

C NODE_

D PUBLIC_

Only variables starting with PUBLIC_ are sent to the client in Remix apps.

Where should you store secret API keys in a Remix app?

A Directly in client-side code

B In variables with PUBLIC_ prefix

C In variables without PUBLIC_ prefix

D In public JSON files

Secrets should be stored in environment variables without PUBLIC_ prefix to keep them server-only.

How do you load environment variables during local development in Remix?

A From a config.json file

B From a .env file at project root

C From the browser localStorage

D From a database

Remix automatically loads variables from a .env file during local development.

Which Remix code can safely access environment variables without PUBLIC_ prefix?

A Server-side loaders and actions

B Client-side React components

C Browser console scripts

D Static HTML files

Server-side code like loaders and actions can access all environment variables safely.

What happens if you try to use a non-prefixed environment variable in client code?

A It will be undefined or not available

B It will be exposed to the client

C It will cause a build error

D It will be encrypted automatically

Non-prefixed variables are not exposed to client code and will be undefined there.

Explain how Remix manages environment variables for client and server code.

Think about how Remix separates client and server environment variables.

Describe best practices for keeping secret keys safe in a Remix app.

Focus on how to avoid leaking secrets to the browser.

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