convex-component-authoring

To publish a reusable Convex component, you structure a project with isolated schemas and functions, define a clear export surface for consuming apps, then use the recommended build configuration for npm publishing.

Having isolated schemas in a Convex component means the data tables, functions, and type definitions are self-contained within the package. This ensures clean separation of concerns and prevents schema conflicts when consuming apps integrate the component.

You export queries and mutations from a Convex package by defining a clear export surface within your component configuration. This provides consuming apps with type-safe interfaces and direct access to the component's functions and hooks.

Yes, you can use TypeScript to build type-safe interfaces for Convex components. The authoring process enforces type definitions and isolated schemas, ensuring consuming apps receive strict type safety across projects.

The recommended project layout for publishing a Convex component to npm includes publishing-ready scaffolding with specific build configurations. This layout enforces component configuration, schema definitions, and exports for dependency management.

You need to configure exports when building reusable Convex packages to establish a clear export surface for consuming apps. This enforces type-safe interfaces and isolates internal functions, preventing unauthorized access to component logic.