feat: add create-prisma next support

[AmanVarshney01]

Summary

• Adds the Prisma Next create flow using prisma-next@latest init --no-install as the source of truth for Prisma Next files and starter contracts.
• Supports PostgreSQL and MongoDB across minimal, hono, elysia, nest, next, svelte, astro, nuxt, and tanstack-start.
• Makes minimal the default template and adds per-template descriptions in the interactive picker.
• Supports PSL and TypeScript contract authoring, with PostgreSQL defaulting to Prisma Postgres in interactive mode and --yes staying non-provisioning.
• Keeps db:init, migrations, and seed manual only. No generated path auto-runs database setup under prompts or --yes.
• Resolves Prisma Next packages from latest at scaffold time instead of hard-pinning framework versions in create-prisma.
• Installs Prisma Next packages, provider runtime packages, generated contract/type packages, and the Vite contract emit plugin where relevant.
• Removes create-prisma ownership of Prisma Next skills sync: no @prisma-next/agent-skill, no skills dependency, no skills:sync script, and no experimental_sync invocation.
• Adds MongoDB Docker Compose helpers for default local MongoDB projects.
• Removes the turborepo template from the Prisma Next create path.
• Simplifies the Clack completion output and adds an agent prompt pointing users to prisma-next.md and the upstream Prisma Next skills/ directory.
• Adds Prisma Next-specific telemetry event names, scoped to create-prisma@next releases.

Validation

• bun run format:check
• bun run typecheck
• bun run lint
• bun run build
• bun run test:unit
• bun run test:e2e
• Full Minimal Postgres flow: install, emit, db:init, db:verify, migration plan/apply, seed, and query script.
• Full Minimal MongoDB flow: install, emit, migration plan/apply, seed, and query script.
• Existing e2e covers Hono Postgres and Hono MongoDB through migrations, seed, generated queries, and build.
• Package-manager smoke for bun, npm, pnpm, and deno verifies generated Minimal projects do not include skills, @prisma-next/agent-skill, or skills:sync.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: ff52e001-4fcb-4203-b6bb-a7f100a62d3b

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch aman/create-prisma-next

✨ Simplify code

• Create PR with simplified code
• Commit simplified code in branch aman/create-prisma-next

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

@next preview published

• Version: 0.4.2-next.37.110.1
• Tag: next
• Trigger: PR has the release:next label, so this is available as create-prisma@next
• Run with Bun: bunx create-prisma@next
• Run with npm: npx create-prisma@next
• Run with Yarn: yarn dlx create-prisma@next
• Run with pnpm: pnpm dlx create-prisma@next
• Run with Deno: deno run -A npm:create-prisma@next
• Workflow run: https://github.com/prisma/create-prisma/actions/runs/26754069067

[AmanVarshney01]

Updated in fca2dac.

What changed

• Aligned generated PostgreSQL code with the current Prisma Next namespace: db.orm.public.User.
• Replaced the removed createCount usage with the current single-row .create(...) API.
• Updated database shutdown paths to use await db.close().
• Raised the required Node.js version to 24 and aligned generated TypeScript dependencies with the Prisma Next 5.9 minimum.
• Added the missing vue-tsc dependency for Nuxt typechecking.
• Excluded generated migrations and Prisma declaration files from Next.js linting.
• Added --no-skill to prisma-next init so scaffolding remains template-driven.
• Updated Mongo helper documentation with its Node.js 24+ requirement.
• Replaced the deprecated tsdown inlineOnly option.
• Expanded template rendering tests to all 180 combinations: 9 templates × 2 providers × 2 authoring modes × 5 package managers.
• Expanded live E2E coverage to all templates and both PSL/TypeScript contracts, including real installs, database lifecycle, migrations, seeds, generated queries, and framework build/typecheck/lint validation.

Verification

• Audited directly against prisma/prisma-next main at e0e739ca6a0e076c97733ef30ec3bf7b1f43a27b.
• Prisma Next latest (0.16.0): 36/36 live Node/npm template combinations passed.
• Prisma Next dev (0.16.0-dev.34): 37/37 tests passed, including positional project-name behavior.
• Unit suite: 37 passed with 1,175 assertions.
• Typecheck, formatting, lint, build, and git diff --check all pass.

Upstream runtime limitation

Bun 1.3.14 + Mongo remains blocked upstream because BSON calls node:v8.startupSnapshot.isBuildingSnapshot(), which Bun currently throws as ERR_NOT_IMPLEMENTED. No Node fallback, BSON pin, shim, or other workaround is retained. Mongo passes across all templates on the supported Node.js 24/npm path.