convex-create-component

Defining the component with defineComponent creates an isolated scope with its own tables and functions. This encapsulates backend logic and prevents data from leaking into the host application, simplifying reuse.

Extracting backend logic into a Convex component enforces app-level authentication and environment handling. The host app manages auth, passing context across the boundary via boundary-walking calls.

The best way to expose a wrapper API is to define clear boundaries for queries, mutations, and actions. The host app accesses these through boundary-walking calls via app.use and the component API.

Yes, you can package Convex functionality for reuse by building a component with an isolated scope and a well-defined app-facing API. Multiple host apps can wire into the same logic using app.use.

Yes, you need to run the codegen or dev workflow after wiring a Convex component with app.use. This generates the server and API stubs required for the host app to communicate across the component boundary.