@prisma-next/config

@prisma-next/config

Internal package. This package is an implementation detail of prisma-next and is published only to support its runtime. Its API is unstable and may change without notice. Do not depend on this package directly; install prisma-next instead.

Config authoring types and validation for prisma-next.config.ts.

Overview

This package owns the shared config contract used by tooling and authoring packages:

• PrismaNextConfig and ContractConfig types
• contract source provider + diagnostics protocol
• provider-declared input metadata for tooling integrations
• defineConfig() normalization/defaulting
• validateConfig() structural/runtime-shape validation

Responsibilities

• Type-safe config composition for family, target, adapter, optional driver, and optional extensionPacks (extensions is rejected at runtime)
• Contract source provider protocol (contract.source) and diagnostics shape
• Tool-agnostic provider input metadata for build integrations via contract.source.inputs
• Pure config validation and normalization with no file system access

Non-responsibilities

• Config file discovery/loading (c12, file I/O) - handled by @prisma-next/cli
• CLI error envelope formatting and rendering - handled by CLI/errors package error utilities
• Control-plane migration operations and runtime actions

Usage

import { defineConfig } from '@prisma-next/config/config-types';
import { validateConfig } from '@prisma-next/config/config-validation';

const config = defineConfig({
  family: sqlFamilyDescriptor,
  target: postgresTargetDescriptor,
  adapter: postgresAdapterDescriptor,
  contract: {
    source: {
      inputs: ['./prisma/schema.prisma'],
      load: async (_context) =>
        /* Result<Contract, ContractSourceDiagnostics> */ null as never,
    },
  },
});

validateConfig(config);

Declare source.inputs only for source files that are not already covered by the config module graph, such as PSL schema paths or TypeScript contract paths passed as strings. Do not include emitted artifact paths derived from contract.output (for example contract.json or the colocated contract.d.ts); the CLI loader resolves and validates those paths before emit/watch commands run. Tooling should always treat the config module graph as watched by default.