Deploy

Goal

This snapshot advances Wavelength Daily by teaching you to deploy Wavelength Daily to Cloudflare Pages.

Each numbered folder is a complete app. Run it independently and compare adjacent snapshots to isolate the new responsibility.

Prerequisites

Use Node.js 20 or newer, npm, and a terminal. Basic TypeScript, HTML, and CSS familiarity will help.

The development server uses port 5173. Database snapshots also need Docker and the Supabase CLI.

• Node.js and npm
• A code editor
• Docker from part 4 onward

Concepts

The Cloudflare adapter targets the Pages runtime while hosted Supabase provides production auth and data.

SvelteKit keeps route UI, server loading, and form actions close together while preserving a clear browser/server boundary.

Walkthrough

Create the hosted project, apply migrations without local seeds, set public variables, and allow Pages callback URLs.

Trace the example from request to rendered page, then inspect the complete matching snapshot for types, validation, and failure handling.

import adapter from '@sveltejs/adapter-cloudflare';

Run and verify

Enter 12-Deploy, install dependencies, and start the app. Supabase stages must start the local stack and copy the printed anon key into .env.

Open http://localhost:5173 and keep the terminal visible so browser actions can be matched to server errors.

git clone https://github.com/michaeldunga1/fcc-sveltekit-blog.git
cd fcc-sveltekit-blog/12-Deploy
npm install
npx supabase start
cp .env.example .env
npm run dev

Troubleshooting

A successful build can still fail at runtime when Pages variables or Supabase redirect URLs are missing.

A missing package usually means npm install ran in another snapshot. After changing environment variables, restart the SvelteKit process.

• Read the first error first
• Check the current snapshot path
• Never commit .env or node_modules

Try this

Deploy, register a fresh account, create a story, and complete one password reset.

Test one happy path and one invalid or unauthorized path before moving on.

• Make one focused change
• Verify it in the browser
• Compare with the next snapshot after it works