docs: align Prisma 8 blogs and guides with the rc.6 CLI and current scaffold - #8153
Merged
Conversation
…caffold Every CLI invocation in the Prisma 8 blogs and v8 guides now uses the unified prisma@next CLI, and the scaffold-dependent steps match what create-prisma@next actually generates today, validated end to end against a live Prisma Postgres database and a local MongoDB replica set. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
🍈 Lychee Link Check Report255 links: ✅ All links are working!Full Statistics Table
|
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (38)
WalkthroughThe PR updates Prisma 8 blog and documentation examples. It replaces legacy CLI commands and configuration, separates database creation from scaffolding, uses ChangesPrisma 8 documentation updates
Estimated code review effort: 4 (Complex) | ~45 minutes ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every CLI invocation in the Prisma 8 blogs and v8 guides now uses the unified
prisma@nextCLI, and the scaffold-dependent steps match whatcreate-prisma@nextgenerates today. All repository links point atprisma/prisma, where the Prisma 8 source now lives.What changed
Commands. Replaced every stale invocation with
npx prisma@next …(or theorm initform for existing projects):npx prisma-next@latest init,pnpx prisma-next init,npx @prisma/cli@next …, andbunx prisma-next …across twelve blog posts and two docs pages. Config snippets that moved commands to the unified CLI also moved toprisma.config.tswith thedefinePrismaConfig/ormConfigwrapper, matching the canonical form in the extensions docs.Scaffold flags.
create-prisma@next(0.4.2-next.37) has no--prisma-postgres,--database-url,--install, or--emitflags; those belong to the Prisma 7 scaffolder (create-prisma@latest0.7.1). Every guide and agent prompt that passed them now scaffolds with the supported flags and gets a database fromnpx create-db@latest(or a connection string the reader already has).Scaffold behavior. The current scaffold is Composer-first: no
.envfor PostgreSQL projects, nodb:seedordb:upscripts, and sample data seeds itself on the app's first query. Neither the CLI nor the dev script reads.envin scaffolded projects (the generated config lacks thedotenv/configimport thatprisma@next orm initwrites), so the quickstarts now exportDATABASE_URLexplicitly. The MongoDB quickstart documents the scaffold's split env contract: the CLI readsMONGODB_URL, the app readsDATABASE_URL. The obsolete PN-CLI-4999 /db.orm.public.Userknown-issue boxes are gone; the scaffold now emits the unified config and namespace-qualified queries.Studio.
prisma@nextrc.6 andprisma@devno longer ship astudiocommand, and the stable Prisma CLI 7.9.1 bundles@prisma/studio-core0.33.0, which includes the Migrations view. The Studio blog and docs page now saynpx prisma@latest studio --url …, run from outside the project directory (the Prisma 7 CLI fails on the Prisma 8prisma.config.ts).Deno. The deno guide's
npm:prisma@nextcommands fail under Deno (ERR_MODULE_NOT_FOUNDin@prisma/credentials-store); the scaffold's generateddeno taskscripts (which callnpm:prisma-next) work, so the guide uses those. The Deno scaffold still takes the legacy path: it provisions a Prisma Postgres database, writes.env, and still needs the documenteddb.orm.public.Userfix, so those parts stay.Repo links.
prisma/prisma-next→prisma/prismaeverywhere the link is a CTA or points at content that moved (examples renamed toprisma-8-demo/prisma-8-postgis-demo; retail-store migration path updated;ROADMAP.mdand thetables.tsdeep link verified to exist inprisma/prisma). Dated milestone PR links stay on the old repo.Not in this PR
search-encrypted-data-with-prisma-8-and-cipherstash); both the published post and the staged draft still usenpx prisma-next …commands and the old config filename, so that session should pick up the same fixes.introducing-create-prismacorrectly documents the Prisma 7 scaffolder (create-prisma@latest) and its--prisma-postgres/--database-urlflags; left as is.Validation
npx create-db@latest→create-prisma@next(minimal template) →npm run db:init(5 operations applied, database signed) →npm run dev→ endpoint returned the 3 seeded users. Confirmed.envalone is read by neither the scripts nor the CLI (db:verifyfails with "Database connection is required" unless the variable is exported).rs0replica set (mongodb-memory-server):npm run migration:plan -- --name init(3 operations) →npm run migrate(applied) →npm run dev→ endpoint returned the 3 seeded users. Confirmed the CLI requiresMONGODB_URLand the app requiresDATABASE_URL.nextandhonotemplates to confirm all templates share the same script set (nodb:seed, no.env).deno task db:init/db:seed/devsucceeded after the documented namespace fix;npm:prisma@nextconfirmed broken under Deno.npx prisma@next orm initvalidated for postgres and mongodb targets (writesprisma.config.tswithdotenv/config; needs--target/--authoringwith--yes).prisma@next studioreturnsCLI.UNKNOWN_COMMAND;npx prisma@latest studio --url …serves Studio from a config-free directory and fails inside a Prisma 8 project.examples/prisma-8-demo,examples/retail-store/migrations/app/20260513T0508_backfill_product_status,packages/3-extensions/*,ROADMAP.md,packages/3-targets/.../tables.ts.pnpm lint:links(0 errors),pnpm run lint:spellcheck(0 issues),pnpm checkclean.🤖 Generated with Claude Code
Summary by CodeRabbit
DATABASE_URL, deployment environment setup, and automatic sample-data seeding on the first query.