refactor: rename to Prisma Compose across packages, CLI, and docs per ADR-0026#57
Merged
Conversation
@prisma/compose
@prisma/compose-alchemy
@prisma/compose-assemble
@prisma/compose-cli
@prisma/compose-cloud
@prisma/compose-nextjs
@prisma/compose-node
@prisma/compose-rpc
prisma-compose
commit: |
wmadden
approved these changes
Jul 12, 2026
Brings ADR-0014 and ADR-0025 into Module terms, per the same rename. These two are the record of the naming decision itself, so this is a coherent rewrite, not a find-replace (a blind swap would make ADR-0025 say "Module leaves the vocabulary entirely" and ADR-0014 reject "Module"). - ADR-0014 rewritten in current Module terms: keeps its still-standing decisions (framework Prisma App, @prisma/app* packages, prisma-app CLI, one authoring primitive module(), App is the outermost Module), drops the pro-System argument and the now-wrong "Module rejected" alternative, and defers the unit noun to ADR-0025. Filename → ADR-0014-name-the-framework-prisma-app.md; all inbound links updated (glossary, layering, naming, naming-proposal, decisions index). - ADR-0025 made self-contained: "System" now appears only as the retired name it documents; references to claims removed from ADR-0014 reworded so nothing dangles; ADR-0014 link retargeted. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
…-compose
Full-surface package/CLI/config rename per ADR-0026 (the framework is Prisma
Compose; "Prisma App" is the artifact):
- packages/app → compose, app-{cloud,node,rpc,nextjs,assemble,cli} → compose-*,
prisma-app → prisma-compose, @prisma/app-tsdown → @prisma/compose-tsdown;
@prisma/alchemy unchanged (independent package). Directory names, every
package.json name + repository.directory, all workspace: deps, and all imports
across packages/examples/test follow.
- CLI binary prisma-app → prisma-compose; config prisma-app.config.ts →
prisma-compose.config.ts (files renamed in every example + test/integration);
scratch dir .prisma-app → .prisma-compose.
- pnpm-lock.yaml + bun.lock renamed in place (workspace:/link: entries; external
versions untouched); .github action + issue template, .agents rules follow.
There is no app-cron package — cron lives in @prisma/compose-cloud/cron.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: willbot <w.a.madden+machine@gmail.com>
Signed-off-by: Will Madden <madden@prisma.io>
Per ADR-0026, the framework is Prisma Compose; "Prisma App" now names only the artifact you build and deploy. - Decision docs: ADR-0014 narrowed to the single-primitive model (framework/ package/CLI names deferred to ADR-0026, unit noun to ADR-0025) and renamed to ADR-0014-one-authoring-primitive.md; ADR-0025 stale CLI/config references updated; decisions README index updated. ADR-0026 documents the retired names (its @prisma/app* / prisma-app mentions are the rename record, like ADR-0025 keeps "System"). - Prose: "Prisma App Framework" → "Prisma Compose" everywhere (README title + opening land the canonical "you build a Prisma App by composing Modules with Prisma Compose"); tool-sense "Prisma App" → "Prisma Compose"; artifact-sense "Prisma App" kept (ADR-0023 "a Prisma App is one Project", "deploy your Prisma App"). Covers docs/design (incl. 04-inspirations), skills, CONTRIBUTING, agent-os, .drive. Judgment calls (artifact-sense keeps + legitimate residuals) are in the PR body. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
pnpm lint was red on a pre-existing biome.jsonc drift (schema pinned 2.4.15 vs the installed 2.5.2 CLI, plus the deprecated `recommended` field). `biome migrate` updates the schema and rewrites `rules.recommended` → `rules.preset: "recommended"`. A valid config then lints fully and surfaced two formatting errors in files this rename touched; `biome format` fixed them. Lint is now green. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
Follows the ADR-0026 amendment merged to main: @prisma/alchemy joins the compose-* family (its independence was a fiction — every published version depends on the core package). packages/alchemy → packages/compose-alchemy; package.json name + repository.directory, all imports/deps, lockfiles, and the core bundle-leanness invariant token follow. The external `alchemy` library (the upstream package we wrap) and "Alchemy" prose are unchanged. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: willbot <w.a.madden+machine@gmail.com> Signed-off-by: Will Madden <madden@prisma.io>
05f405a to
5ea412d
Compare
wmadden
approved these changes
Jul 12, 2026
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
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.
Full-surface rename of the framework from "Prisma App" to Prisma Compose,
per ADR-0026.
"Prisma App" now names only the artifact a user builds and deploys.
What changed
Packages (
refactor):@prisma/app→@prisma/compose;app-{cloud,node,rpc,nextjs,assemble,cli}→compose-*; theprisma-appCLI package →prisma-compose;@prisma/app-tsdown→@prisma/compose-tsdown.@prisma/alchemyis unchanged (independent). Directory names, everypackage.jsonname+repository.directory, allworkspace:deps, and all imports follow. Lockfiles (pnpm-lock.yaml,bun.lock) renamed in place —workspace:/link:entries only, external versions untouched.CLI + config: binary
prisma-app→prisma-compose;prisma-app.config.ts→prisma-compose.config.ts(renamed in every example +test/integration); scratch dir.prisma-app/→.prisma-compose/. CLI help/errors/generated output, the.githubdeploy action + issue template, and.agentsrules follow.Docs prose:
"Prisma App Framework"→Prisma Composeeverywhere; README title + opening land the canonical sentence "you build a Prisma App by composing Modules with Prisma Compose." Tool-sensePrisma App→Prisma Compose; artifact-sensePrisma Appkept. Coversdocs/design/**(incl.04-inspirations),skills,CONTRIBUTING,agent-os,.drive.Decision docs (step 0): ADR-0026's Decision/Consequences were already full-surface on #55. ADR-0014 narrowed to the single-primitive model (framework/package/CLI deferred to ADR-0026, unit noun to ADR-0025) and renamed
→ ADR-0014-one-authoring-primitive.md; ADR-0025's incidental stale CLI/config references fixed; decisions README index +naming.md/vocabulary-tests.mdupdated.Judgment calls (artifact-sense keeps)
Per the substitute test ("the user's application" → keep; "the tool" → rename):
Acceptance
pnpm build/typecheck/test/test:types— all green (build 14, typecheck 30, test 25, test:types 17). A bundle-leanness invariant test that resolved adapters by the oldpackages/app-nodepath was updated.grep -rn "Prisma App Framework"→ zero.grep -rn "prisma/app\b\|@prisma/app\|prisma-app" packages examples docs README.md skills→ only: the repo URL (github.com/prisma/app.git), ADR-0023's artifact-sense filename links, and ADR-0026 documenting the retired names (the rename record — the analog of ADR-0025 keeping "System").Flags / coordination
pnpm linthas 2 pre-existing errors unrelated to this rename — biome.jsonc config drift ($schemapins 2.4.15 while the pinned CLI is 2.5.2, plus a deprecatedrecommendedfield). Present onmain; every lint diagnostic is in a file this rename does not touch. Left alone to avoid changing lint-rule semantics.docs/oss/versioning.mdcovers pre-1.0 minor bumps but not package renames. The@prisma/app*packages at0.2.0-devwill need a deprecation strategy (final deprecated publish pointing at@prisma/compose*, or a README pointer) — flagging for a maintainer call rather than inventing policy.docs/prisma-compose, ADR-0026) and subsumes docs(adr): finish System → Module in the naming ADRs (ADR-0014/0025) #56 (the ADR-0014/0025 System→Module cleanup, cherry-picked here). Merging this lands all three; docs: ADR-0026 — the framework is Prisma Compose; 'Prisma App' names the artifact #55 and docs(adr): finish System → Module in the naming ADRs (ADR-0014/0025) #56 can then be closed.@prisma/alchemy, and ADR-0025's decision are untouched.🤖 Generated with Claude Code