create-mailslot 0.1.1 → 0.2.1

package/README.md

@@ -1,9 +1,9 @@
 # create-mailslot
 
-Deploy [Mailslot](https://github.com/mailslot/mailslot) — a self-hosted email
-inbox for AI agents — to your own Cloudflare account, interactively.
+> A real inbox for AI agents. Self-hosted.
 
-> Your agent's email shouldn't come with a landlord.
+Deploy [Mailslot](https://github.com/mailslot/mailslot) to your own Cloudflare
+account, interactively.
 
 ```sh
 npx create-mailslot
@@ -11,29 +11,29 @@ npx create-mailslot
 
 The wizard:
 
-1. **Scaffolds a project you own** — a thin worker depending on
-   `@mailslot/core`, deployed from your machine with wrangler
-2. **Guards your existing mail** — if the domain's apex already receives
-   mail elsewhere (Google Workspace, Lark, O365…), the wizard tells you the
-   truth: Email Routing is zone-level, so that domain can't host Mailslot —
-   not even on a subdomain — without breaking its mail. It steers you to a
-   different domain instead of letting you find out the hard way
-3. **Provisions everything** — R2 bucket, generated API token (secret),
-   worker deploy with your domain baked in
-4. **Sets up Email Routing** — fully automatic with a Cloudflare API token
-   (`Zone → Email Routing Rules → Edit`), or guided dashboard steps with
-   live DNS verification if you'd rather click
-5. **Proves it works** — ends with a live round-trip: send an email from
-   your phone, watch it appear in your terminal
-
-## Flags (all optional — omitted values are prompted)
+1. **Scaffolds a project you own.** A thin worker depending on `@mailslot/core`,
+   deployed from your machine with wrangler.
+2. **Guards your existing mail.** If the domain's apex already receives mail
+   elsewhere (Google Workspace, Lark, O365, and so on), the wizard tells you the
+   truth: Email Routing is zone-level, so that domain cannot host Mailslot, not
+   even on a subdomain, without breaking its mail. It steers you to a different
+   domain instead of letting you find out the hard way.
+3. **Provisions everything.** R2 bucket, a generated API token (secret), and a
+   worker deploy with your domain baked in.
+4. **Sets up Email Routing.** Fully automatic with a Cloudflare API token
+   (`Zone → Email Routing Rules → Edit`), or guided dashboard steps with live
+   DNS verification if you'd rather click.
+5. **Proves it works.** Ends with a live round-trip: send an email from your
+   phone, watch it appear in your terminal.
+
+## Flags (all optional, omitted values are prompted)
 
 ```
 --dir <path>           project directory            (default: mailslot)
 --domain <domain>      email domain on Cloudflare   (e.g. mail.example.com)
 --worker-name <name>   worker name                  (default: mailslot)
 --cf-token <token>     Cloudflare API token for Email Routing setup
---core-spec <spec>     @mailslot/core version/spec  (default: ^0.0.2)
+--core-spec <spec>     @mailslot/core version/spec  (default: matches this wizard's version)
 --skip-install / --skip-routing / --skip-test
 ```
 

package/lib/run.js

@@ -1,4 +1,5 @@
 import { randomBytes } from "node:crypto";
+import { readFileSync } from "node:fs";
 import { writeFile } from "node:fs/promises";
 import { join, resolve } from "node:path";
 import * as p from "@clack/prompts";
@@ -7,6 +8,10 @@ import { mxRecords, isCloudflareMx, isCloudflareNs, findZone, waitForCloudflareM
 import { templates, writeScaffold } from "./scaffold.js";
 import { zoneId, routingStatus, enableRouting, setCatchAllToWorker } from "./cf-api.js";
 
+// Wizard and core ship in lockstep (same repo version), so the inbox we
+// scaffold should depend on the core that matches THIS wizard's version.
+const selfVersion = JSON.parse(readFileSync(new URL("../package.json", import.meta.url), "utf8")).version;
+
 export function parseArgs(argv) {
   const flags = {};
   for (let i = 0; i < argv.length; i++) {
@@ -133,7 +138,7 @@ export async function run(argv) {
   const routingReady = isCloudflareMx(domainMx);
 
   // ---- scaffold ----
-  const coreSpec = flags["core-spec"] ?? "^0.0.2";
+  const coreSpec = flags["core-spec"] ?? `^${selfVersion}`;
   const files = templates({ workerName, coreSpec });
   await writeScaffold(dir, files);
   p.log.success(`Scaffolded ${dir}`);

package/lib/scaffold.js

@@ -1,8 +1,11 @@
 import { mkdir, readdir, writeFile } from "node:fs/promises";
 import { join, dirname } from "node:path";
 
-/** Render the files of a scaffolded Mailslot project. */
-export function templates({ workerName, coreSpec = "^0.0.2" }) {
+/** Render the files of a scaffolded Mailslot project.
+ *  coreSpec (e.g. "^0.2.0") is required — run.js derives it from the wizard's
+ *  own version so the scaffold can't drift from the core it shipped with. */
+export function templates({ workerName, coreSpec }) {
+  if (!coreSpec) throw new Error("templates: coreSpec is required");
   const pkg = {
     name: workerName,
     private: true,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-mailslot",
-  "version": "0.1.1",
+  "version": "0.2.1",
   "description": "Deploy Mailslot — a self-hosted email inbox for AI agents — to your own Cloudflare account.",
   "license": "MIT",
   "type": "module",