convex-component-authoring

To create reusable Convex components, you define a clear directory layout, isolate database tables in schema.ts, implement functions in src/functions, and export them from src/index.ts. This structure ensures self-contained components share seamlessly across projects.

Publishing a Convex component package requires configuring package.json and tsconfig.json. You define your component's schema, functions, and exports in standard directories, then publish the package to npm for consumption by other Convex applications.

The best way to export queries and mutations from a Convex component is to implement them in src/functions and aggregate them through main exports in src/index.ts. This ensures consuming applications can access the isolated functions seamlessly.

Yes, you can use published Convex components in an existing Convex application. The Skill provides usage examples illustrating how to integrate and call the exported queries, mutations, and actions from the npm package directly into your app.

Separate package.json and tsconfig.json configurations are needed for Convex components to manage dependencies and TypeScript compilation properly. This setup ensures the isolated schema, functions, and types are correctly bundled for npm publishing and cross-project consumption.

You should avoid isolated database tables in a Convex component if your data requires direct, shared access across multiple uncoordinated applications or if your functions need to query the main application's database schema directly without component boundaries.