convex-create-component

To create reusable Convex components, you build component-local schema and functions with isolated tables, then install them via `app.use(...)` and expose well-typed public wrappers using `ctx.runQuery`, `ctx.runMutation`, or `ctx.runAction` for app-side wiring.

The best way to extract reusable Convex components is to choose a component shape—local, packaged, or hybrid—implement component-local schema and functions, then wire app-side auth-aware wrappers for clients.

Authentication across Convex component boundaries requires keeping auth in the app layer while passing explicit values across the boundary, ensuring the reusable component itself remains boundary-safe and doesn't directly access environment authentication.

Yes, you can package Convex functionality for reuse across apps by creating a hybrid or packaged component that owns its tables and exposes small, well-typed functions, then installing it in each app using `app.use`.

You should not use a packaged Convex component when authentication or environment access cannot be kept in the app layer, as Convex components require boundary-safe auth and explicit value passing rather than direct internal access.

Yes, you need to define a component-local `schema.ts` when building a Convex component to ensure the component owns its isolated tables and maintains clean boundaries from the main application code.