Deploying to Cloudflare Workers in Remix - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to import the Cloudflare adapter for Remix.

Remix

import { [1] } from '@remix-run/cloudflare';

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

AcreateCloudflareAdapter

BcreateCloudflareWorker

CcreateCloudflareHandler

DcreateCloudflare

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'createCloudflareHandler' which does not exist.

Importing 'createCloudflareWorker' which is incorrect.

The correct import is createCloudflareAdapter which sets up Remix to run on Cloudflare Workers.

2fill in blank

medium

Complete the code to export the Remix handler for Cloudflare Workers.

Remix

export default [1](remixHandler);

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

AcreateCloudflareWorker

BcreateCloudflareHandler

CcreateCloudflareAdapter

DcreateCloudflare

Attempts:

3 left

💡 Hint

Common Mistakes

Using a non-existent function like 'createCloudflareWorker'.

Forgetting to wrap the handler with the adapter.

You export the Remix handler wrapped by createCloudflareAdapter to run on Cloudflare Workers.

3fill in blank

hard

Fix the error in the Cloudflare Workers deployment script by completing the environment variable access.

Remix

export default [1](remixHandler, { env: [2].ENV });

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

AcreateCloudflareAdapter

Bprocess

CglobalThis

Dself

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'process' which is not available in Cloudflare Workers.

Not wrapping the handler with the adapter function.

The deployment script must use createCloudflareAdapter to wrap the handler and pass environment variables correctly. The environment variables are accessed via self.ENV in Cloudflare Workers.

4fill in blank

hard

Fill both blanks to correctly define the Cloudflare Worker entry point and export.

Remix

addEventListener('[1]', event => {
  event.respondWith([2](event.request));
});

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

Afetch

BcreateCloudflareAdapter

ChandleRequest

Drequest

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect event names like 'request' or 'handle'.

Not using the adapter function to respond.

The Cloudflare Worker listens for the 'fetch' event and uses createCloudflareAdapter to handle requests.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that filters environment variables for Cloudflare deployment.

Remix

const envVars = Object.fromEntries(
  Object.entries(env).filter(([[1], [2]]) => [3].startsWith('CF_'))
);

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

Akey

Bvalue

Denv

Attempts:

3 left

💡 Hint

Common Mistakes

Using 'env' instead of 'key' in the filter condition.

Swapping key and value in destructuring.

This code extracts environment variables whose keys start with 'CF_'. The entries are filtered by key.

Practice

1. What is the main benefit of deploying a Remix app to Cloudflare Workers?

easy

A. Your app runs fast and scales worldwide without managing servers.

B. You get a built-in database for your app.

C. It automatically converts your app to a mobile app.

D. It disables JavaScript to improve security.

Solution

1. Step 1: Understand Cloudflare Workers role

   Cloudflare Workers run code at the edge, close to users, improving speed and scalability.

2. Step 2: Recognize Remix deployment benefits

   Deploying Remix to Cloudflare Workers means no server management and fast global delivery.

3. Final Answer:

   Your app runs fast and scales worldwide without managing servers. -> Option A

4. Quick Check:

   Cloudflare Workers = fast, scalable, no servers [OK]

Hint: Cloudflare Workers run code globally without servers [OK]

Common Mistakes:

• Thinking Cloudflare Workers provide a database
• Assuming it converts apps to mobile automatically
• Believing it disables JavaScript

2. Which command correctly deploys a Remix app to Cloudflare Workers?

easy

A. npm start cloudflare-workers

B. npm run deploy -- --target=cloudflare-workers

C. remix deploy cloudflare

D. npm run build-cloudflare

Solution

1. Step 1: Identify deployment command format

   Remix uses npm scripts with flags to specify deployment targets.

2. Step 2: Match correct command

   The documented command is npm run deploy -- --target=cloudflare-workers.

3. Final Answer:

   npm run deploy -- --target=cloudflare-workers -> Option B

4. Quick Check:

   Deploy command uses --target=cloudflare-workers [OK]

Hint: Use npm run deploy with --target=cloudflare-workers [OK]

Common Mistakes:

• Using npm start instead of npm run deploy
• Omitting the --target flag
• Using incorrect command names

3. Given this snippet in remix.config.js:

module.exports = {
  serverBuildTarget: "cloudflare-workers",
  server: "./server.js"
};

What happens when you run npm run build?

medium

A. It builds the app targeting Cloudflare Workers environment.

B. It throws an error because serverBuildTarget is invalid.

C. It builds a Node.js server app instead of Cloudflare Workers.

D. It skips building and only runs tests.

Solution

1. Step 1: Understand serverBuildTarget setting

   Setting serverBuildTarget to "cloudflare-workers" tells Remix to build for that platform.

2. Step 2: Effect of running npm run build

   Running npm run build compiles the app for the specified target without errors.

3. Final Answer:

   It builds the app targeting Cloudflare Workers environment. -> Option A

4. Quick Check:

   serverBuildTarget = cloudflare-workers means build targets Workers [OK]

Hint: serverBuildTarget sets build environment [OK]

Common Mistakes:

• Assuming serverBuildTarget is invalid
• Confusing Cloudflare Workers with Node.js target
• Thinking build skips and runs tests

4. You run npm run deploy -- --target=cloudflare-workers but get an error: Cannot find module '@cloudflare/wrangler'. What should you do?

medium

A. Restart your computer and try again.

B. Change the target to 'node' and redeploy.

C. Delete node_modules and run npm run build again.

D. Install the Wrangler package with npm install -D @cloudflare/wrangler.

Solution

1. Step 1: Identify missing module error cause

   The error means the Wrangler tool needed for Cloudflare deployment is not installed.

2. Step 2: Fix by installing Wrangler

   Installing Wrangler as a dev dependency fixes the missing module error.

3. Final Answer:

   Install the Wrangler package with npm install -D @cloudflare/wrangler. -> Option D

4. Quick Check:

   Missing module = install Wrangler [OK]

Hint: Missing module? Install it with npm install -D [OK]

Common Mistakes:

• Changing target instead of installing missing package
• Only deleting node_modules without reinstalling
• Restarting computer without fixing dependencies

5. You want to deploy a Remix app to Cloudflare Workers but also use environment variables securely. Which approach is best?

hard

A. Hardcode environment variables in your Remix code before deploying.

B. Store environment variables in a public JSON file served by Remix.

C. Use Cloudflare Workers environment variables configured via Wrangler's wrangler.toml file.

D. Pass environment variables as URL query parameters.

Solution

1. Step 1: Understand secure environment variable usage

   Hardcoding or exposing env vars publicly is insecure and bad practice.

2. Step 2: Use Wrangler config for secure env vars

   Wrangler's wrangler.toml supports secure environment variables for Workers.

3. Final Answer:

   Use Cloudflare Workers environment variables configured via Wrangler's wrangler.toml file. -> Option C

4. Quick Check:

   Secure env vars = wrangler.toml config [OK]

Hint: Use wrangler.toml for secure env vars [OK]

Common Mistakes:

• Hardcoding secrets in code
• Exposing secrets in public files
• Passing secrets in URLs