A modern, opinionated starter template for building fast, accessible web applications.

• Astro v7 - Modern web framework with server-first rendering
• React v19 - UI library for interactive components
• TypeScript v6 - Type-safe JavaScript
• Tailwind CSS v4 - Utility-first CSS framework
• Supabase - Authentication and backend-as-a-service
• Cloudflare Workers - Edge deployment runtime

• Node.js v26.13.0 (as specified in .nvmrc)
• npm (comes with Node.js)

1. Clone the repository:

git clone https://github.com/przeprogramowani/10x-astro-starter.git
cd 10x-astro-starter

2. Install dependencies:

npm install

3. Set up Supabase and configure environment variables — see Supabase Configuration below.

4. Create a .dev.vars file for local Cloudflare dev secrets:

cp .env.example .dev.vars

5. Run the development server:

npm run dev

• npm run dev - Start development server (Cloudflare workerd runtime)
• npm run build - Build for production
• npm run preview - Preview production build
• npm run lint - Run ESLint with type-checked rules
• npm run lint:fix - Auto-fix ESLint issues
• npm run format - Run Prettier
• npm run smoke - Smoke test the auth flow against a running server (BASE_URL, defaults to http://localhost:4321)

.
├── src/
│ ├── layouts/ # Astro layouts
│ ├── pages/ # Astro pages
│ │ └── api/ # API endpoints
│ ├── components/ # UI components (Astro & React)
│ └── assets/ # Static assets
├── public/ # Public assets
├── wrangler.jsonc # Cloudflare Workers config

This project uses Supabase for authentication. Environment variables are declared via Astro's astro:env schema and are treated as server-only secrets — they are never exposed to the client.

Requires Docker and ~7 GB RAM.

1. Create your .env file:

cp .env.example .env

2. Initialize the local Supabase project (creates a supabase/ config folder):

npx supabase init

3. Start the local stack (downloads Docker images on first run):

npx supabase start

4. Copy the credentials printed by the CLI into your .env and .dev.vars:

SUPABASE_URL=http://127.0.0.1:54321
SUPABASE_KEY=<anon key from CLI output>

5. To stop the stack when done:

npx supabase stop

The local Studio UI is available at http://localhost:54323.

No database tables or migrations are required — this project uses Supabase Auth's built-in auth.users table only.

If you prefer to use a hosted Supabase project, add these variables to your .env and .dev.vars files:

SUPABASE_URL=https://<project-ref>.supabase.co
SUPABASE_KEY=<anon-key>

By default Supabase requires email confirmation before a user can sign in. To skip this during local development:

1. Open the Supabase dashboard for your project
2. Go to Authentication → Email → Confirm email
3. Toggle it off

Users can then sign in immediately after sign-up without clicking a confirmation link.

Route protection is handled in src/middleware.ts. Add paths to the PROTECTED_ROUTES array there to require authentication.

This project deploys to Cloudflare Workers.

1. Build the project:

npm run build

2. Deploy with Wrangler:

npx wrangler deploy

Set SUPABASE_URL and SUPABASE_KEY as secrets in your Cloudflare dashboard or via npx wrangler secret put.

scripts/smoke.mjs is a dependency-free Node script that walks the whole auth flow (sign-up, sign-in, protected page, sign-out) over HTTP. Run it against the dev server or the production preview after dependency upgrades:

npm run dev            # or: npm run build && npm run preview
BASE_URL=http://localhost:4321 npm run smoke

It needs a reachable Supabase instance (local or cloud) with email confirmation disabled.

Note: this script exists primarily to guard the development of the starter itself — it is a fast sanity check that dependency upgrades did not break the build, the Cloudflare adapter or the Supabase auth flow. It is not a substitute for a real test suite. Once you build your own product on top of this starter, add proper tests (unit, integration, end-to-end) suited to your application.

GitHub Actions runs two jobs on every push and PR to master:

• ci — lint, astro check and build. Configure SUPABASE_URL and SUPABASE_KEY as repository secrets for the build step.
• smoke — starts a local Supabase via the Supabase CLI, builds, serves the production preview on the Cloudflare runtime and runs npm run smoke against it. No secrets required.

MIT