Skip to content

refactor: rename to Prisma Compose across packages, CLI, and docs per ADR-0026#57

Merged
wmadden merged 5 commits into
mainfrom
claude/prisma-compose-rename
Jul 12, 2026
Merged

refactor: rename to Prisma Compose across packages, CLI, and docs per ADR-0026#57
wmadden merged 5 commits into
mainfrom
claude/prisma-compose-rename

Conversation

@wmadden-electric

Copy link
Copy Markdown
Contributor

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-*; the prisma-app CLI package → prisma-compose; @prisma/app-tsdown@prisma/compose-tsdown. @prisma/alchemy is unchanged (independent). Directory names, every package.json name + repository.directory, all workspace: deps, and all imports follow. Lockfiles (pnpm-lock.yaml, bun.lock) renamed in place — workspace:/link: entries only, external versions untouched.

There is no app-cron package — cron ships as @prisma/compose-cloud/cron, so "app-cron → compose-cron" didn't apply.

CLI + config: binary prisma-appprisma-compose; prisma-app.config.tsprisma-compose.config.ts (renamed in every example + test/integration); scratch dir .prisma-app/.prisma-compose/. CLI help/errors/generated output, the .github deploy action + issue template, and .agents rules follow.

Docs prose: "Prisma App Framework"Prisma Compose everywhere; README title + opening land the canonical sentence "you build a Prisma App by composing Modules with Prisma Compose." Tool-sense Prisma AppPrisma Compose; artifact-sense Prisma App kept. Covers docs/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.md updated.

Judgment calls (artifact-sense keeps)

Per the substitute test ("the user's application" → keep; "the tool" → rename):

  • ADR-0023 "a Prisma App is one Prisma Cloud Project", "deploy your Prisma App", README "you build a Prisma App", "In a Prisma App each of those…" — all artifact-sense, kept (incl. ADR-0023's filename).
  • Tool-sense hits renamed: "Prisma App owns composition", "Prisma App spans three planes", "built with Prisma App", "Prisma App infers…".

Acceptance

  • pnpm build / typecheck / test / test:typesall green (build 14, typecheck 30, test 25, test:types 17). A bundle-leanness invariant test that resolved adapters by the old packages/app-node path 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

🤖 Generated with Claude Code

@pkg-pr-new

pkg-pr-new Bot commented Jul 12, 2026

Copy link
Copy Markdown

Open in StackBlitz

@prisma/compose

npm i https://pkg.pr.new/prisma/app/@prisma/compose@57

@prisma/compose-alchemy

npm i https://pkg.pr.new/prisma/app/@prisma/compose-alchemy@57

@prisma/compose-assemble

npm i https://pkg.pr.new/prisma/app/@prisma/compose-assemble@57

@prisma/compose-cli

npm i https://pkg.pr.new/prisma/app/@prisma/compose-cli@57

@prisma/compose-cloud

npm i https://pkg.pr.new/prisma/app/@prisma/compose-cloud@57

@prisma/compose-nextjs

npm i https://pkg.pr.new/prisma/app/@prisma/compose-nextjs@57

@prisma/compose-node

npm i https://pkg.pr.new/prisma/app/@prisma/compose-node@57

@prisma/compose-rpc

npm i https://pkg.pr.new/prisma/app/@prisma/compose-rpc@57

prisma-compose

npm i https://pkg.pr.new/prisma/app/prisma-compose@57

commit: 5ea412d

wmadden-electric and others added 5 commits July 12, 2026 18:30
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>
@wmadden-electric wmadden-electric force-pushed the claude/prisma-compose-rename branch from 05f405a to 5ea412d Compare July 12, 2026 16:34
@wmadden wmadden merged commit fe0b40f into main Jul 12, 2026
14 checks passed
@wmadden wmadden deleted the claude/prisma-compose-rename branch July 12, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants