orpc-contract-first

Contract-first API development is enforced by defining API contracts as a single source of truth, scoping new oRPC contract layers, and migrating existing calls to contract-driven patterns for stable input/output types.

A single source of truth for API contracts is a centralized definition in the web/contract directory that maintains type safety and reduces boilerplate by preventing scattered request details across client code.

Migrating existing API calls to contract-driven patterns involves scoping new oRPC contract layers to replace scattered request details, ensuring all client-server communication adheres to predefined stable input and output types.

Contract-first API development reduces boilerplate by centralizing API definitions, which minimizes scattered request details in frontend client code and ensures interactions maintain stable input and output types.

oRPC contracts support both backend and frontend development by establishing a single source of truth for API interactions, ensuring stable types and structured client-server communication across the TypeScript stack.

Contract-first API development is needed when your project requires structured API stability and maintainability, specifically addressing the need to enforce a single source of truth for stable input/output types.