create-jant 0.3.13 → 0.3.15

package/README.md

@@ -71,16 +71,16 @@ my-site/
 ## Scripts
 
 ```bash
-pnpm dev           # Start dev server (http://localhost:9019)
-pnpm build         # Build for production
-pnpm cf:deploy        # Build + deploy to Cloudflare Workers
-pnpm typecheck     # Run TypeScript checks
-pnpm lint          # Run ESLint
-pnpm format        # Format code with Prettier
-pnpm db:generate   # Generate Drizzle migrations
-pnpm db:migrate:local   # Apply migrations (local)
-pnpm db:migrate:remote  # Apply migrations (production)
-pnpm i18n:build    # Extract + compile translations
+pnpm dev               # Start dev server (http://localhost:9019)
+pnpm build             # Build for production
+pnpm run deploy        # Build + deploy to Cloudflare Workers
+pnpm typecheck         # Run TypeScript checks
+pnpm lint              # Run ESLint
+pnpm format            # Format code with Prettier
+pnpm db:generate       # Generate Drizzle migrations
+pnpm db:migrate:local  # Apply migrations (local)
+pnpm db:migrate:remote # Apply migrations (production)
+pnpm i18n:build        # Extract + compile translations
 ```
 
 ## License

package/dist/index.js

@@ -9,7 +9,7 @@ import path from "path";
 import { fileURLToPath } from "url";
 var __filename = fileURLToPath(import.meta.url);
 var __dirname = path.dirname(__filename);
-var CORE_VERSION = "0.3.13";
+var CORE_VERSION = "0.3.15";
 var TEMPLATE_DIR = fs.existsSync(path.resolve(__dirname, "../template")) ? path.resolve(__dirname, "../template") : path.resolve(__dirname, "../../../templates/jant-site");
 function isValidProjectName(name) {
   return /^[a-z0-9]([a-z0-9-]*[a-z0-9])?$/.test(name);
@@ -91,6 +91,7 @@ async function copyTemplate(config) {
       if (basename === "reset-local.sql") return false;
       if (basename === "seed-local.sql") return false;
       if (basename === "export-demo.mjs") return false;
+      if (basename === "export-seed.mjs") return false;
       return true;
     }
   });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-jant",
-  "version": "0.3.13",
+  "version": "0.3.15",
   "description": "Create a new Jant project",
   "type": "module",
   "bin": {

package/template/README.md

@@ -2,7 +2,7 @@
 
 A personal website/blog powered by [Jant](https://github.com/jant-me/jant).
 
-## Getting Started
+## Local Development
 
 ```bash
 pnpm dev
@@ -12,7 +12,19 @@ Visit http://localhost:9019 to see your site.
 
 ## Deploy to Cloudflare
 
-### 1. Prerequisites
+### Option A: One-Click Deploy
+
+[![Deploy to Cloudflare](https://deploy.workers.cloudflare.com/button)](https://deploy.workers.cloudflare.com/?url=https://github.com/jant-me/jant-starter)
+
+Click the button, name your Worker, D1 database, and R2 bucket, set `AUTH_SECRET` (32+ random characters), and you're done!
+
+After deploying, set `SITE_URL` in Cloudflare dashboard → your Worker → Settings → Variables.
+
+> If you deployed via the button, skip to [Custom Domain](#custom-domain-optional).
+
+### Option B: Manual Deployment
+
+#### 1. Prerequisites
 
 Install [Wrangler CLI](https://developers.cloudflare.com/workers/wrangler/install-and-update/) and log in:
 
@@ -20,7 +32,7 @@ Install [Wrangler CLI](https://developers.cloudflare.com/workers/wrangler/instal
 wrangler login
 ```
 
-### 2. Create D1 Database
+#### 2. Create D1 Database
 
 Check the `database_name` in your `wrangler.toml` (defaults to `<your-project>-db`), then create it:
 
@@ -29,18 +41,18 @@ wrangler d1 create <your-project>-db
 # Copy the database_id from the output!
 ```
 
-### 3. Update Configuration
+#### 3. Update Configuration
 
 Edit `wrangler.toml`:
 
 - Replace `database_id = "local"` with the ID from step 2
-- Set `SITE_URL` to your production URL
+- Set `SITE_URL` to your production URL (e.g. `https://example.com`)
 
 > R2 bucket is automatically created on first deploy — no manual setup needed.
 >
-> **Note:** Changing `database_id` resets your local development database (local data is stored per database ID). This is why we recommend setting up deployment before starting local development.
+> **Note:** Changing `database_id` resets your local development database (local data is stored per database ID). If you've already started local development, you'll need to go through the setup wizard again to create your admin account.
 
-### 4. Set Production Secrets
+#### 4. Set Production Secrets
 
 Generate a production secret and save it somewhere safe (you'll need it again for CI):
 
@@ -55,19 +67,16 @@ wrangler secret put AUTH_SECRET
 
 > **Important:** This is separate from the `AUTH_SECRET` in `.dev.vars` (which is for local development only). Do not change the production secret after your site is live — it will invalidate all sessions. If you get locked out, use `pnpm reset-password` to generate a password reset link.
 
-### 5. Deploy
+#### 5. Deploy
 
 ```bash
-# Apply database migrations to production
-pnpm db:migrate:remote
-
-# Build and deploy
-pnpm cf:deploy
+# Apply database migrations and deploy
+pnpm run deploy
 ```
 
 Your site is now live at `https://<your-project>.<your-subdomain>.workers.dev`!
 
-### 6. Custom Domain (Optional)
+### Custom Domain (Optional)
 
 1. Go to [Cloudflare Dashboard](https://dash.cloudflare.com) → Workers & Pages
 2. Select your worker → Settings → Domains & Routes
@@ -75,7 +84,7 @@ Your site is now live at `https://<your-project>.<your-subdomain>.workers.dev`!
 
 ## GitHub Actions (CI/CD)
 
-A workflow file is included at `.github/workflows/deploy.yml`. Complete the [manual deployment](#deploy-to-cloudflare) first, then set up CI for automatic deployments.
+A workflow file is included at `.github/workflows/deploy.yml`. Complete the [manual deployment](#option-b-manual-deployment) first, then set up CI for automatic deployments.
 
 > Runtime secrets (`AUTH_SECRET`, S3 keys, etc.) are already stored in Cloudflare from the manual deployment step. CI only needs deployment credentials.
 
@@ -86,7 +95,7 @@ Create a new repository on [GitHub](https://github.com/new), then commit and pus
 ```bash
 git add -A
 git commit -m "Initial setup"
-git remote add origin https://github.com/<your-username>/<your-repo>.git
+git remote add origin git@github.com:<your-username>/<your-repo>.git
 git push -u origin main
 ```
 
@@ -148,17 +157,23 @@ jobs:
       CF_ACCOUNT_ID: ${{ secrets.CF_ACCOUNT_ID }}
 ```
 
+### Cloudflare Workers Builds (Alternative CI/CD)
+
+Workers Builds is auto-configured if you used the [One-Click Deploy](#option-a-one-click-deploy) button. To enable auto-deploy on push, go to Cloudflare dashboard → Workers → your worker → Settings → Builds.
+
 ## Commands
 
 | Command                  | Description                        |
 | ------------------------ | ---------------------------------- |
 | `pnpm dev`               | Start development server           |
 | `pnpm build`             | Build for production               |
-| `pnpm cf:deploy`         | Build and deploy to Cloudflare     |
+| `pnpm run deploy`        | Migrate, build, and deploy         |
 | `pnpm preview`           | Preview production build           |
 | `pnpm typecheck`         | Run TypeScript checks              |
 | `pnpm db:migrate:remote` | Apply database migrations (remote) |
 
+> `deploy` uses `pnpm run deploy` because `pnpm deploy` is a built-in pnpm command. All other scripts work with or without `run`.
+
 ## Environment Variables
 
 | Variable      | Description                               | Location         |
@@ -235,20 +250,19 @@ export default createApp({
 ## Updating
 
 ```bash
-# Update @jant/core
-pnpm update @jant/core
+# Update @jant/core to latest version
+pnpm add @jant/core@latest
 
 # Start dev server (auto-applies migrations locally)
 pnpm dev
 
-# Before deploying: apply migrations to production
-pnpm db:migrate:remote
-
-# Deploy
-pnpm cf:deploy
+# Deploy (includes remote migrations)
+pnpm run deploy
 ```
 
-> New versions of `@jant/core` may include database migrations. Always run `pnpm db:migrate:remote` before deploying after an update. Check the [release notes](https://github.com/jant-me/jant/releases) for any breaking changes.
+> New versions of `@jant/core` may include database migrations. Check the [release notes](https://github.com/jant-me/jant/releases) for any breaking changes.
+>
+> **Dev dependencies** (vite, wrangler, tailwindcss, etc.) may also need updating. Compare your `devDependencies` with the [latest template](https://github.com/jant-me/jant/blob/main/templates/jant-site/package.json) and update if needed.
 
 ## Documentation
 

package/template/package.json

@@ -5,10 +5,10 @@
   "type": "module",
   "packageManager": "pnpm@10.28.2",
   "scripts": {
-    "dev": "pnpm db:migrate:local && vite dev",
-    "dev:debug": "pnpm db:migrate:local && vite dev --port 19019",
+    "dev": "pnpm run db:migrate:local && vite dev",
+    "dev:debug": "pnpm run db:migrate:local && vite dev --port 19019",
     "build": "vite build",
-    "cf:deploy": "pnpm build && wrangler deploy",
+    "deploy": "pnpm run db:migrate:remote && pnpm run build && wrangler deploy",
     "preview": "vite preview",
     "typecheck": "tsc --noEmit",
     "db:migrate:local": "yes | wrangler d1 migrations apply DB --local",

package/template/scripts/seed-demo.sql

@@ -82,7 +82,7 @@ cd my-blog
 pnpm dev
 
 # Deploy to Cloudflare
-pnpm cf:deploy
+pnpm run deploy
 ```
 
 ## Documentation
@@ -147,7 +147,7 @@ cd my-blog
 pnpm dev
 
 # Deploy to Cloudflare
-pnpm cf:deploy
+pnpm run deploy
 </code></pre>
 <h2>Documentation</h2>
 <ul>