feat: add Prisma 8 support - #37
Merged
Merged
Conversation
|
Important Review skippedToo many files! This PR contains 159 files, which is 9 over the limit of 150. To get a review, reduce the PR to 150 files or fewer by splitting it into smaller PRs or changing its base branch. Upgrade to Pro+ to raise the limit. This review couldn't start because sufficient usage credits or metered capacity aren't available. Add credits or update usage-based reviews in the billing tab, then retry. ⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (159)
You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Comment |
AmanVarshney01
added
the
release:next
@next preview published
|
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
* feat: use mongodb-memory-server for local mongo dev Replace the docker-compose helper with a generated scripts/start-mongo.ts that runs mongodb-memory-server, so `db:up` works without Docker. When mongo is selected without --database-url, the helper now writes the start script, pins mongodb-memory-server@^11.1.0 as a devDependency, and sets a package-manager-aware `db:up` script (bun / deno run -A / tsx). No more docker-compose.yml, no db:down. The e2e suite is parameterized across hono + next for both providers (4 tests). Mongo cases scaffold without a databaseUrl, start the generated db:up in the background on a free port, and exercise migrate / seed / verify / build against the in-memory server — so the generated script is itself under test. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat: persist mongo dev data across db:up restarts The generated scripts/start-mongo.ts now writes the replica set's data to a real directory (default .mongo-data/, overridable via MONGO_DB_PATH) instead of mongodb-memory-server's temp dir, so seeded users and applied migrations survive between Ctrl+C cycles. The setup helper gitignores .mongo-data, and each template README explains the "delete the folder for a clean slate" escape hatch. E2E tests stay ephemeral by construction: each test scaffolds a fresh project, so its .mongo-data is a fresh directory too. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * feat: detach db:up and add db:down + db:reset Replace scripts/start-mongo.ts with a scripts/mongo.ts CLI that exposes three subcommands: up (detached child that exits once the replica set prints "ready", PID written to .mongo-data/mongo.pid, logs in .mongo-data/mongo.log), down (SIGTERM the recorded PID, SIGKILL after 10s, idempotent on stale PIDs), and reset (down plus wipe of .mongo-data/). The CLI re-exec's itself with the right runner — bun, deno run -A, or tsx — so it stays correct across the package managers we ship. Cleanup is now an obvious one-liner: db:reset stops mongo and removes the data directory. db:down leaves data in place. The e2e suite is correspondingly simpler: the test just calls `bun run db:up` (returns when ready, MONGO_PORT passed in for collision-free parallelism) and `bun run db:down` in the finally, with no in-test background process management. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * fix: harden local mongo scaffold Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: clean up mongo helper data paths Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> --------- Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Aman Varshney <amanvarshney.work@gmail.com>
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
* refactor: model Prisma Next version as a resolved spec Introduce ResolvedPrismaNextSpec + parsePrismaNextVersionSpec so the target Prisma Next version is no longer a module-level constant. The parser recognises pkg-pr-new:<ref> specs alongside npm versions and dist-tags; getPrismaNextPackageSpecifier and getDependencyVersion now accept the resolved spec and emit either name@<spec> or the https://pkg.pr.new/prisma/prisma-next/<name>@<ref> URL form that package managers accept directly. No call sites pass a non-default spec yet; the new shape is what the upcoming --prisma-next-version flag will thread through. * feat: thread --prisma-next-version through scaffolding Add the --prisma-next-version flag and plumb the resolved Prisma Next spec into PrismaSetupContext, writePrismaDependencies, writeCreateTemplateDependencies, and the prisma-next init invocation. Every @prisma-next/* and prisma-next dependency written into package.json — and the npx/dlx/bunx prisma-next@<spec> init command — now honours the spec. With no flag, behaviour is unchanged (latest). Supported specs: - a published npm version (0.10.0, 0.11.0-dev.9, …) for regression / bisect work against the exact version a user filed an issue on; - an npm dist-tag (latest, dev, next, …) for smoke-testing release candidates before they get the latest tag; - pkg-pr-new:<sha|branch|pr-number> for dogfooding open PRs end-to-end through the canonical scaffold path — substitutes the https://pkg.pr.new/prisma/prisma-next/<package>@<ref> URL specifier for every Prisma Next install. Package managers accept URL specifiers in both install argv and package.json, so no special-casing per package manager is needed. The pkg.pr.new path doesn't yet derive a matching skills ref (the upstream prisma-next CLI needs a PRISMA_NEXT_SKILLS_REF override before this is fully wired up); cases 1+2 work end-to-end today and unblock the onboarding-audit regression workflows. * feat: report Prisma Next version spec in create telemetry Add prisma-next-version-kind (default | npm-tag | npm-version | pkg-pr-new) and prisma-next-version-spec to the create command's completion / failure events. The kind is the low-cardinality signal the onboarding audit needs to see which escape hatch users reach for; the spec round-trips the exact string for the long tail of dist-tags, prereleases, and PR refs that can't be summarised by the kind alone.
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
Closed
4 tasks
Member
Author
|
Updated in What changed
Verification
Upstream runtime limitationBun 1.3.14 + Mongo remains blocked upstream because BSON calls |
* feat: add Prisma Composer workflow Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: update tsdown dependency warning config Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: isolate generated TypeScript contract artifacts Write emitted contract JSON and types to a generated directory so TypeScript does not resolve contract.d.ts to the adjacent contract.ts source file. Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: pin the Prisma platform CLI prerelease Use the aligned RC2 package for init, authentication, and Composer commands so package-manager tag caches cannot resolve an older CLI without the ORM command. Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: show deployed app URL * fix: expose Elysia on Compute * fix: select the Elysia runtime adapter * fix: address deploy matrix failures * fix: align Composer framework dependencies * fix: bundle SvelteKit runtime dependencies Keep SvelteKit on adapter-node while asking Vite to inline the application runtime packages required by the self-contained Composer build artifact. Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: inline all SvelteKit SSR dependencies Use Vite noExternal for the full server dependency graph so the adapter-node build is self-contained for Composer. Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: default immediate deployment to yes Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * chore: call the release Prisma 8 Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: consume released framework deployment fixes Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: connect and seed starter databases Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: keep seeding on public Composer bindings Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * fix: seed through Composer service runtime Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com> * refactor: align Prisma 8 templates with consolidated CLI * chore: update Composer packages to 0.9 --------- Signed-off-by: Aman Varshney <amanvarshney.work@gmail.com>
AmanVarshney01
added
release:next
AmanVarshney01
marked this pull request as ready for review
August 18, 2026 15:09
AmanVarshney01
marked this pull request as draft
August 18, 2026 15:10
AmanVarshney01
marked this pull request as ready for review
August 21, 2026 13:19
AmanVarshney01
changed the title
Member
Author
|
@coderabbitai approve |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
✅ Action performedComments resolved and changes approved. |
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
3 participants
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.
Summary
prisma-next@latest init --no-installas the source of truth for Prisma Next files and starter contracts.minimal,hono,elysia,nest,next,svelte,astro,nuxt, andtanstack-start.minimalthe default template and adds per-template descriptions in the interactive picker.--yesstaying non-provisioning.db:init, migrations, and seed manual only. No generated path auto-runs database setup under prompts or--yes.latestat scaffold time instead of hard-pinning framework versions in create-prisma.@prisma-next/agent-skill, noskillsdependency, noskills:syncscript, and noexperimental_syncinvocation.prisma-next.mdand the upstream Prisma Nextskills/directory.create-prisma@nextreleases.Validation
bun run format:checkbun run typecheckbun run lintbun run buildbun run test:unitbun run test:e2edb:init,db:verify, migration plan/apply, seed, and query script.bun,npm,pnpm, anddenoverifies generated Minimal projects do not includeskills,@prisma-next/agent-skill, orskills:sync.