@moneydevkit/create 0.3.2 → 0.4.0-beta.0

package/README.md

@@ -5,7 +5,8 @@ Developer onboarding CLI for Money Dev Kit. This package publishes the interacti
 ## Getting Started
 
 1. Run `npx @moneydevkit/create@latest` from the root of your project. The CLI walks you through login, webhook verification, and writes your secrets to `.env.local` (or a path you pick) while also copying them to the clipboard by default.
-2. Follow the prompts. When you reach your editor again, `MDK_ACCESS_TOKEN`, `MDK_WEBHOOK_SECRET`, and `MDK_MNEMONIC` are ready to go.
+2. If we detect a Next.js app (package.json `next` dependency, `next.config.*`, or an `app/` directory), we'll offer to install and scaffold `@moneydevkit/nextjs` for you.
+3. Follow the prompts. When you reach your editor again, `MDK_ACCESS_TOKEN` and `MDK_MNEMONIC` are ready to go.
 
 ### Customize the flow with flags
 
@@ -15,7 +16,7 @@ Pass any of the options from the table below to skip prompts or run non-interact
 npx @moneydevkit/create@latest \
   --dir ./apps/storefront \
   --env-target .env.production \
-  --webhook-url https://example.com/webhooks/mdk \
+  --webhook-url https://example.com \
   --project-name "Storefront" \
   --no-open --no-clipboard
 ```
@@ -36,6 +37,14 @@ The CLI still creates a device code but immediately authorises it using your coo
 2. Launches the browser for sign-in (or prints the verification URL when `--no-open` or `--json` are supplied).
 3. Polls until the dashboard authorises the device, then provisions an API key + webhook secret, and generates a mnemonic locally via BIP-39.
 4. Shows an env diff, writes `.env.local` (or a user-specified file), and optionally copies secrets to the clipboard.
+5. Detects a Next.js app and (with your confirmation or `--scaffold-nextjs`) installs `@moneydevkit/nextjs`, wraps `next.config.*` with `withMdkCheckout`, and scaffolds the API route plus `/checkout/[id]` page without overwriting existing files.
+
+## Next.js scaffolding
+
+- Auto-detects Next.js via `package.json`, `next.config.*`, or `app/` directory. If found, you'll be prompted to install and scaffold `@moneydevkit/nextjs`. Requires Next.js 15+ (per SDK peer deps).
+- `--scaffold-nextjs` forces the install/scaffold (useful for CI); if no Next.js app is found, the CLI prints a warning and skips.
+- Always scaffolds App Router files (`app/api/mdk/route.(ts|js)` and `app/checkout/[id]/page.(tsx|js)`).
+- Existing files are left untouched; `next.config.*` is backed up if we need to wrap it with `withMdkCheckout`.
 
 ## Flags
 
@@ -49,8 +58,9 @@ The CLI still creates a device code but immediately authorises it using your coo
 | `--no-clipboard` | Do not place secrets on the clipboard. |
 | `--json` | Emit JSON result payloads (no interactive prompts).
 | `--manual-login "<cookie>"` | Use a pre-generated dashboard session cookie instead of device flow. |
-| `--webhook-url "<url>"` | Provide the webhook URL when running in `--manual-login` or `--json` modes. |
+| `--webhook-url "<url>"` | Provide the domain when running in `--manual-login` or `--json` modes. |
 | `--force-new-webhook` | Force creation of a new webhook even if one already exists for the URL. |
+| `--scaffold-nextjs` | Force install + scaffold `@moneydevkit/nextjs` (warns and skips if no Next.js app is detected). |
 
 Manual login mode calls `POST /api/cli/device/authorize` with the supplied session cookie. When used with `--json`, pass `--webhook-url` to avoid interactive prompts.
 
@@ -65,8 +75,25 @@ npm run run:local    # talk to a dashboard at http://localhost:3900
 
 ## Releasing to npm
 
-1. Bump the version in `packages/create/package.json` (for example: `npm version 0.2.0 --workspace packages/create --no-git-tag-version`) and commit the resulting `package-lock.json` change.
-2. Push the commit, then create a GitHub release (or annotated tag) named `create-vX.Y.Z` that matches the new version string.
-3. The `publish-create` workflow will detect that tag, run the build, and execute `npm publish packages/create --access public` using trusted publishing.
+All `@moneydevkit/*` packages share a unified version number and are released together.
+
+### Beta releases (automatic)
+
+Every push to `main` that modifies files in `packages/` triggers the `publish-beta` workflow:
+1. All packages are bumped to the next beta version (e.g., `0.4.0-beta.0` → `0.4.0-beta.1`)
+2. All packages are published to npm with the `beta` tag
+
+Install the latest beta with:
+```bash
+npx @moneydevkit/create@beta
+npm install @moneydevkit/nextjs@beta
+```
+
+### Stable releases
+
+1. Create a GitHub release with a tag matching the version in package.json (e.g., if package.json has `0.4.0-beta.3`, create tag `v0.4.0`)
+2. The `publish-release` workflow validates, publishes, and bumps to the next minor version
 
 Once that workflow succeeds, `npx @moneydevkit/create@latest` automatically downloads the freshly published build.
+
+See the [main README](../../README.md#releasing) for version flow examples and error cases.