prisma-composer-core-concepts

Declare what a node requires in its deps ports and wire producers to consumers inside a Module builder using provision(). Because ports are typed, the TypeScript compiler verifies every wire, so mismatches fail tsc rather than the deploy.

Deploys are replay-only: they apply migrations committed under migrations/ and never create schema. Edit contract.prisma, run prisma contract emit, then prisma migration plan, commit the migrations, and deploy; skipping the plan step causes MIGRATION_PATH_NOT_FOUND.

Composer mints a per-binding service key at deploy and serve() returns 401 to any caller that is not a wired consumer. This is expected behavior, not a broken deploy; debug through a wired consumer or locally where nothing is enforced.

The alchemy engine pins an exact effect version, and a hoisted newer effect from your app or a dependency halts every command. Match your app's effect to @prisma/composer's pin or force it with overrides in package.json, then reinstall.

Yes. Use mockService from @prisma/composer/testing to substitute typed dependency doubles in unit tests, or bootstrapService from @prisma/composer-prisma-cloud/testing to boot the real built entry in-process and drive it over real HTTP.

There is no interactive CLI login (deploys use a static PRISMA_SERVICE_TOKEN), no in-memory contract bindings, and RPC over HTTP is the only contract kind. Windows is not supported for local dev, and streamed HTTP responses time out at the ingress.