This package provides TypeScript type definitions and JSON Schemas for Prisma Next data contracts. The data contract is the canonical description of an application's data model and storage layout, independent of any specific query language or database target.

Responsibilities

Core Contract Types: Defines framework-level contract types (ContractBase, Source) that are shared across all target families
Document Family Types: Provides TypeScript types for document target family contracts (DocumentContract)
JSON Schema Validation: Provides JSON Schemas for validating contract structure in IDEs and tooling
Type Guards: Provides runtime type guards for narrowing contract types (isDocumentContract)
Emitter Types: Defines emitter SPI types (TargetFamilyHook, ValidationContext, TypesImportSpec) that are shared between emitter and control plane

The contract supports document target families:

Document: For document databases (MongoDB, Firestore, etc.)

Package Contents

TypeScript Types: Type definitions for DocumentContract, ContractMarkerRecord, and related types
Emitter Types: SPI types for emitter hooks (TargetFamilyHook, ValidationContext, TypesImportSpec)
JSON Schemas: Schema definitions for validating contract.json files in IDEs and tooling
- data-contract-document-v1.json (Document family)

Usage

TypeScript Types

Import contract types in your TypeScript code:

import type {
  ContractMarkerRecord,
  DocumentContract,
  TargetFamilyHook,
  TypesImportSpec,
  ValidationContext,
} from '@prisma-next/contract/types';
import { isDocumentContract } from '@prisma-next/contract/types';

// Use type guards to narrow the contract type
function processContract(contract: DocumentContract) {
  if (isDocumentContract(contract)) {
    // contract is DocumentContract
    console.log(contract.storage.document.collections);
  }
}

// Use ContractMarkerRecord for database marker operations
function processMarker(marker: ContractMarkerRecord) {
  console.log(marker.coreHash, marker.profileHash);
}

// Use emitter types for implementing family hooks
const myFamilyHook: TargetFamilyHook = {
  id: 'my-family',
  validateTypes: (ir, ctx: ValidationContext) => {
    // Validation logic
  },
  validateStructure: (ir) => {
    // Structure validation
  },
  generateContractTypes: (ir, codecTypeImports: TypesImportSpec[], operationTypeImports: TypesImportSpec[]) => {
    // Type generation
    return '// Generated types...';
  },
};

JSON Schema Validation

Reference the appropriate JSON schema in your contract.json files to enable IDE validation and autocomplete.

Document Family

For document targets (MongoDB, Firestore, etc.):

{
  "$schema": "node_modules/@prisma-next/contract/schemas/data-contract-document-v1.json",
  "schemaVersion": "1",
  "target": "mongodb",
  "targetFamily": "document",
  "coreHash": "sha256:...",
  "storage": {
    "document": {
      "collections": {
        "users": {
          "name": "users",
          "fields": {
            "id": { "type": "objectId", "nullable": false },
            "email": { "type": "string", "nullable": false }
          }
        }
      }
    }
  }
}

Note: For SQL contracts, use @prisma-next/sql-query/schema-sql instead:

{
  "$schema": "node_modules/@prisma-next/sql-query/schemas/data-contract-sql-v1.json",
  "schemaVersion": "1",
  "target": "postgres",
  "targetFamily": "sql",
  "coreHash": "sha256:...",
  "storage": {
    "tables": {
      "user": {
        "columns": {
          "id": { "type": "int4", "nullable": false },
          "email": { "type": "text", "nullable": false }
        },
        "primaryKey": {
          "columns": ["id"],
          "name": "user_pkey"
        }
      }
    }
  }
}

After installing this package, IDEs like VS Code will automatically:

Validate your contract structure
Provide autocomplete for properties
Show descriptions and constraints in tooltips
Highlight errors for invalid configurations

Schema Reference

Common Header Fields

All contracts share these common fields:

schemaVersion (required): Contract schema version (currently "1")
target (required): Database target identifier (e.g., "postgres", "mongo", "firestore")
targetFamily (required): Target family classification ("document" for document contracts)
coreHash (required): SHA-256 hash of the core schema structure
profileHash (optional): SHA-256 hash of the capability profile
capabilities (optional): Capability flags declared by the contract
extensions (optional): Extension packs and their configuration
meta (optional): Non-semantic metadata (excluded from hashing)
sources (optional): Read-only sources (views, etc.) available for querying

Document Family Structure

storage.document.collections: Object mapping collection names to collection definitions
- Each collection includes:
  - name: Logical collection name
  - id (optional): ID generation strategy (auto, client, uuid, cuid, objectId)
  - fields: Field definitions using FieldType (supports nested objects and arrays)
  - indexes (optional): Array of index definitions with keys and optional predicates
  - readOnly (optional): Whether mutations are disallowed

Type System

Type Guards

Use type guards to narrow the contract type:

import { isDocumentContract } from '@prisma-next/contract/types';

if (isDocumentContract(contract)) {
  // TypeScript knows contract is DocumentContract
  const collections = contract.storage.document.collections;
}

Exports

./types: TypeScript type definitions and type guards
./schema-document: Document family JSON Schema (schemas/data-contract-document-v1.json)

Architecture

flowchart TD
    subgraph "Contract Package"
        TYPES[Type Definitions]
        SCHEMA[JSON Schemas]
        GUARDS[Type Guards]
    end

    subgraph "Consumers"
        EMITTER[Emitter]
        RUNTIME[Runtime]
        QUERY[Query Builder]
    end

    TYPES --> EMITTER
    TYPES --> RUNTIME
    TYPES --> QUERY
    SCHEMA --> EMITTER
    GUARDS --> RUNTIME
    GUARDS --> QUERY

Data Contract: Detailed subsystem specification
Contract Emitter & Types: Contract emission

Dependencies

@prisma-next/operations: For OperationRegistry type used in ValidationContext and TargetFamilyHook
Note: This package depends on @prisma-next/operations, but @prisma-next/operations does not depend on this package (no cycle). The OperationRegistry type is used in emitter SPI types that are shared between migration-plane and shared-plane packages.

Dependents:

@prisma-next/contract-authoring: Uses core contract types for authoring
@prisma-next/sql-contract: Extends core contract types for SQL family
@prisma-next/emitter: Uses contract types for emission
@prisma-next/runtime: Uses contract types for runtime execution
@prisma-next/sql-query: Uses contract types for query building

@prisma-next/sql-query: SQL query builder and plan types
@prisma-next/runtime: Runtime execution engine that consumes contracts

FAQs

What is @prisma-next/contract?

Is @prisma-next/contract popular?

Is @prisma-next/contract well maintained?

Package last updated on 18 Dec 2025

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

@prisma-next/contract