convex-component-authoring

To create reusable Convex components, you define a self-contained schema, functions, and exports, then publish them to npm. This isolation ensures your component's tables and logic remain separated from the host app's data.

The best way to structure a Convex component for publishing is to ensure it is self-contained with its own schema, isolated tables, clear exports, and proper dependency management, followed by documentation for distribution.

Yes, you need a TypeScript project setup with a Convex component configuration to build and share components. This setup ensures proper typing, isolation of schemas, and correct export management for distribution.

Component isolation works by keeping the component's tables, schema, and functions self-contained and separated from the host app's data. The host app imports and wires the component into its Convex configuration without direct table access.

Yes, you can version and reuse Convex components across multiple apps. By publishing the isolated component package to npm, different host applications can consume the specific version and wire it into their Convex configuration.