Deployment

Honeycomb deploys to Cloudflare Pages using the official SvelteKit adapter. The build produces a Pages-compatible output that runs on the Cloudflare Workers runtime.

Adapter setup

The Cloudflare adapter is configured in svelte.config.js:

svelte.config.js

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

/** @type {import('@sveltejs/kit').Config} */
const config = {
  kit: {
    adapter: adapter()
  }
};

export default config;

The adapter takes no additional options — the defaults work for Pages deployments. It compiles SvelteKit’s server-side code into a Cloudflare Workers-compatible format and places the output in .svelte-kit/cloudflare/.

Package: @sveltejs/adapter-cloudflare (v7.x)

Wrangler configuration

wrangler.toml

name = "honeycomb"
compatibility_date = "2025-03-01"
pages_build_output_dir = ".svelte-kit/cloudflare"
compatibility_flags = ["nodejs_compat"]

Key fields

Field	Value	Purpose
name	"honeycomb"	Project name in Cloudflare dashboard
compatibility_date	"2025-03-01"	Pins the Workers runtime to this date’s behavior
pages_build_output_dir	".svelte-kit/cloudflare"	Output directory the adapter writes to
compatibility_flags	["nodejs_compat"]	Enables Node.js built-in modules

Caution

The pages_build_output_dir field is required. Without it, Cloudflare ignores wrangler.toml entirely and compatibility flags will not apply. The build log will show “Skipping file and continuing” if this is missing.

nodejs_compat flag

The nodejs_compat compatibility flag enables Node.js built-in modules on the Workers runtime. Honeycomb requires this for:

• node:crypto — used by Supabase Auth and Stripe SDK for cryptographic operations
• node:async_hooks — used internally by some dependencies

Without this flag, any import of node:* modules will fail at runtime with a “module not found” error.

Build process

Local build

npm run build

This runs vite build, which:

1. Compiles all Svelte components and TypeScript
2. Bundles client-side assets with code-splitting
3. Generates the server-side Worker via the Cloudflare adapter
4. Outputs everything to .svelte-kit/cloudflare/

Preview locally

npm run preview

Serves the built output using Vite’s preview server. Note that this does not use the Cloudflare Workers runtime — for a production-accurate preview, use wrangler pages dev:

npx wrangler pages dev .svelte-kit/cloudflare

Type checking

npm run check

Runs svelte-kit sync (generates type declarations) followed by svelte-check against the TypeScript config.

Cloudflare Pages deployment

Git integration (recommended)

Connect the GitHub repository to Cloudflare Pages in the dashboard:

1. Go to Workers & Pages in the Cloudflare dashboard
2. Create a new Pages project and connect the repository
3. Set the build configuration:
   • Build command: npm run build
   • Build output directory: .svelte-kit/cloudflare
   • Root directory: / (or the monorepo subdirectory if applicable)

Cloudflare will automatically build and deploy on every push to the production branch, with preview deployments for pull requests.

Direct upload

Alternatively, deploy a local build directly:

npm run build
npx wrangler pages deploy .svelte-kit/cloudflare --project-name honeycomb

Environment variables

Environment variables are managed in the Cloudflare Pages dashboard under Settings > Environment variables. SvelteKit accesses them via two import paths:

Server-only (private)

import { STRIPE_SECRET_KEY } from "$env/static/private";

Only available in +server.ts, +page.server.ts, +layout.server.ts, and hooks.server.ts. Never sent to the browser.

Client-safe (public)

import { PUBLIC_SUPABASE_URL } from "$env/static/public";

Prefixed with PUBLIC_. Inlined into the client bundle at build time.

Required variables

Variable	Visibility	Description
PUBLIC_SUPABASE_URL	Public	Supabase project URL
PUBLIC_SUPABASE_ANON_KEY	Public	Supabase anonymous/public key
SUPABASE_SERVICE_ROLE_KEY	Private	Supabase service role key (full access)
STRIPE_SECRET_KEY	Private	Stripe API secret key
STRIPE_WEBHOOK_SECRET	Private	Stripe webhook signing secret
OPENAI_API_KEY	Private	OpenAI API key for AI features

Danger

Never prefix secret keys with PUBLIC_. Any variable starting with PUBLIC_ is embedded in the client JavaScript bundle and visible to all users.

Environment-specific values

Cloudflare Pages supports separate variable sets for Production and Preview environments. Use different Supabase projects or Stripe test keys for preview deployments to avoid polluting production data.

Compatibility date

The compatibility_date in wrangler.toml pins the Workers runtime behavior. Cloudflare rolls out breaking changes behind date-gated flags. Setting 2025-03-01 means the runtime behaves as it did on that date.

To adopt newer runtime features, bump the date forward and test thoroughly. Check the Cloudflare compatibility dates documentation for a changelog of what each date enables.

Database types

Supabase TypeScript types are generated from the live schema and committed to the repository:

npm run db:types

This runs:

npx supabase gen types typescript --project-id "$PROJECT_REF" > src/lib/types/database.ts

Set the PROJECT_REF environment variable to your Supabase project reference ID before running this command. Regenerate types whenever the database schema changes.