create-prisma 0.1.4 → 0.2.0-pr.17.22.1

package/README.md

@@ -1,6 +1,6 @@
 # create-prisma
 
-A modern Prisma 7 CLI with first-party project templates and great init DX.
+A modern Prisma 7 CLI with first-party project templates and a smooth create flow.
 
 ## Stack
 
@@ -20,97 +20,170 @@ Run directly with Bun:
 bunx create-prisma@latest
 ```
 
-Create a new project (default command):
+Run directly with Yarn:
+
+```bash
+yarn dlx create-prisma@latest
+```
+
+Run directly with Deno:
+
+```bash
+deno run -A npm:create-prisma@latest
+```
+
+Create a new project in an empty directory:
+
+```bash
+create-prisma
+```
+
+Initialize Prisma in the current project:
 
 ```bash
 create-prisma
 ```
 
+Create a new project explicitly:
+
+```bash
+create-prisma create
+```
+
 Create a Hono project non-interactively:
 
 ```bash
-create-prisma --name my-api --template hono --provider postgresql
+create-prisma create --name my-api --template hono --provider postgresql
 ```
 
 Create a Next.js project non-interactively:
 
 ```bash
-create-prisma --name my-web --template next --provider postgresql
+create-prisma create --name my-web --template next --provider postgresql
 ```
 
-Initialize Prisma explicitly in the current project:
+Create a SvelteKit project non-interactively:
 
 ```bash
-create-prisma init
+create-prisma create --name my-app --template svelte --provider postgresql
+```
+
+Create an Astro project non-interactively:
+
+```bash
+create-prisma create --name my-site --template astro --provider postgresql
+```
+
+Create a Nuxt project non-interactively:
+
+```bash
+create-prisma create --name my-nuxt-app --template nuxt --provider postgresql
+```
+
+Create a TanStack Start project non-interactively:
+
+```bash
+create-prisma create --name my-start-app --template tanstack-start --provider postgresql
+```
+
+Create a Turborepo project with a `packages/db` Prisma package:
+
+```bash
+create-prisma create --name my-monorepo --template turborepo --provider postgresql
 ```
 
 Set package manager non-interactively:
 
 ```bash
-create-prisma init --package-manager pnpm --install
+create-prisma create --name my-app --template hono --package-manager pnpm --install
 ```
 
 Skip Prisma Client generation:
 
 ```bash
-create-prisma init --no-generate
+create-prisma create --name my-app --template hono --no-generate
 ```
 
 Show verbose command output:
 
 ```bash
-create-prisma init --verbose
+create-prisma create --name my-app --template hono --verbose
 ```
 
-Run fully non-interactive with defaults:
+Scaffold a new project non-interactively with defaults:
 
 ```bash
-create-prisma init --yes
+create-prisma create --yes
 ```
 
 Use Prisma Postgres auto-provisioning for PostgreSQL:
 
 ```bash
-create-prisma init --provider postgresql --prisma-postgres
+create-prisma create --name my-app --template hono --provider postgresql --prisma-postgres
+```
+
+Enable add-ons with individual flags:
+
+```bash
+create-prisma create --name my-app --template next --skills --mcp --extension
 ```
 
 Or run locally:
 
 ```bash
 bun install
+bun run check
 bun run build
 bun run start
 ```
 
-The CLI updates `package.json` with Prisma dependencies, optionally runs dependency installation with your selected package manager, and scaffolds Prisma 7 setup files from Handlebars templates:
+The CLI updates `package.json` with Prisma dependencies, optionally runs dependency installation with your selected package manager, and scaffolds Prisma 7 setup files directly inside each app template:
+
 - `prisma/schema.prisma`
-- `prisma/index.ts`
+- `prisma/seed.ts`
+- `src/lib/prisma.ts`, `src/lib/prisma.server.ts`, `src/lib/server/prisma.ts`, `server/utils/prisma.ts`, or `packages/db/src/client.ts`
 - `prisma.config.ts`
+- `src/generated/prisma` or `server/generated/prisma` (Nuxt) or `packages/db/src/generated/prisma` (Turborepo)
 - `.env` (creates or updates `DATABASE_URL`, and writes `CLAIM_URL` when Prisma Postgres is provisioned)
 - runs `prisma generate` automatically after scaffolding
 
+The create flow is smart:
+
+- if the current directory contains a `package.json` and you do not pass `--name`, `--template`, `--force`, `--skills`, `--mcp`, or `--extension`, it initializes Prisma in the current project
+- otherwise it scaffolds a new project
+- passing `create` explicitly, or passing `--name` or `--template`, forces the project scaffolding flow
+
 `create` is the default command and currently supports:
-- templates: `hono`, `next`
+
+- templates: `hono`, `next`, `svelte`, `astro`, `nuxt`, `tanstack-start`, `turborepo`
 - project name via `--name`
 - schema presets via `--schema-preset empty|basic` (default: `basic`)
 
-`init` configures Prisma in the current project and supports schema presets too (default: `empty`).
-Both commands prompt for database choice, package manager, and whether to install dependencies now.
+When initializing an existing project, it adds the standard Prisma setup from the dedicated init template, auto-detects the existing package manager, and asks where to place the Prisma instance file, defaulting to `src/lib/prisma.ts`.
+
+`create` prompts for database choice, package manager, and whether to install dependencies now.
 Supported providers in this flow: `postgresql`, `mysql`, `sqlite`, `sqlserver`, `cockroachdb`.
-Supported package managers: `bun`, `pnpm`, `npm`.
+Supported package managers: `bun`, `deno`, `npm`, `pnpm`, `yarn`.
 Package manager prompt auto-detects from `package.json`/lockfiles/user agent and uses that as the initial selection.
 `--yes` accepts defaults (`postgresql`, detected package manager, Prisma Postgres enabled for PostgreSQL, install enabled) and skips prompts.
 `--no-generate` skips automatic `prisma generate`.
 `--verbose` prints full install/generate command output; default mode keeps output concise.
-`--force` (create only) allows scaffolding in a non-empty target directory.
-If Prisma files already exist, `init` asks whether to keep existing files or overwrite them.
-When `postgresql` is selected, `init` can provision Prisma Postgres via `create-db --json` and auto-fill `DATABASE_URL`.
+`--force` allows scaffolding in a non-empty target directory when creating a new project.
+Add-ons can be selected interactively or through flags: `--skills`, `--mcp`, `--extension`.
+When add-ons are enabled, `create` prompts for the relevant agent and IDE selections, then installs curated Prisma skills (`skills@latest`), configures Prisma MCP (`add-mcp@latest`), and installs the Prisma IDE extension for supported IDE CLIs.
+When `postgresql` is selected, `create` can provision Prisma Postgres via `create-db --json` and auto-fill `DATABASE_URL`.
+Generated projects also include `db:seed` and configure Prisma's `migrations.seed` hook to run the package-manager-appropriate Prisma seed command.
 
 ## Scripts
 
 - `bun run build` - Build to `dist/`
+- `bun run check` - Run formatting and lint checks
 - `bun run dev` - Watch mode build
 - `bun run start` - Run built CLI
+- `bun run lint` - Run `oxlint` with warnings treated as failures
+- `bun run lint:fix` - Apply safe `oxlint` fixes
+- `bun run format` - Format the repo with `oxfmt`
+- `bun run format:check` - Check formatting with `oxfmt`
 - `bun run typecheck` - TypeScript checks only
 - `bun run bump` - Create a release PR (interactive semver bump)
 - `bun run bump -- patch|minor|major|x.y.z` - Non-interactive bump
@@ -124,5 +197,8 @@ This repo uses a manual, script-driven release flow:
 1. Run `bun run bump` (or pass `patch|minor|major|x.y.z`).
 2. The script creates a `release/vX.Y.Z` branch and a PR with commit `chore(release): X.Y.Z`.
 3. Merge that PR to `main` with squash (keep commit title `chore(release): X.Y.Z`).
-4. GitHub Actions creates the `vX.Y.Z` tag and GitHub Release notes via `changelogithub`.
-5. GitHub Actions publishes only for `chore(release):` commits, using npm trusted publishing (OIDC, no npm token secret).
+4. GitHub Actions runs `bun run check`, `bun run typecheck`, and `bun run build` before publishing.
+5. GitHub Actions creates the `vX.Y.Z` tag and GitHub Release notes via `changelogithub`.
+6. GitHub Actions publishes only for `chore(release):` commits, using npm trusted publishing (OIDC, no npm token secret).
+
+Every PR from a branch in this repository also publishes a preview package to npm using the dist-tag `pr<PR_NUMBER>`, so PR 3 is installable as `create-prisma@pr3`.

package/dist/cli.mjs

@@ -1,5 +1,5 @@
 #!/usr/bin/env node
-import "./create-Dz9GFGFQ.mjs";
+import "./create-CyMasmHY.mjs";
 import { createCreatePrismaCli } from "./index.mjs";
 
 //#region src/cli.ts