Use `@next-model/supabase-connector` to back a `@next-model/core` Model with Supabase via `@supabase/supabase-js` (PostgREST). One connector for both server (service_role) and browser (anon) — only the client/key differs. Triggers include "Supabase connector", "Model on Supabase", "PostgREST ORM". DDL/transactions/raw SQL are unsupported (manage schema with Supabase migrations).
arktype schema bridge for next-model — a single `@next-model/arktype` object type drives the Model's `init` coercer, `validators`, AND `createTable` columns. Triggers on "arktype model", "type-syntax schema", "single source of truth Model + DB", or any request to wire arktype into next-model.
Use when wiring `@next-model/aurora-data-api-connector` to talk to AWS Aurora Serverless v1 over the RDS Data API. Triggers include "Aurora connector", "RDSDataClient", "Lambda + Aurora", and HTTP-based access to Aurora Postgres or MySQL clusters with no VPC tunnel.
Core of `@next-model/core`, a typed promise-based ORM and Model factory for TypeScript. Trigger when the user wants to "define a model", build chainable queries with `filterBy`, set up a `MemoryConnector`, declare associations, write a schema DSL, attach validators, enable soft delete, or otherwise reach for an ORM API surface (`Model({...})`, `defineSchema`, `defineTable`, `unscoped`, `paginate`, `transaction`).
Use `@next-model/express-rest-api` to expose a `@next-model/core` Model as a conventional REST resource on Express 5. Triggers include "expose model over Express REST", "REST adapter", "8 default CRUD actions", "auth hooks per action", and "response mapping".
GraphQL schema generator for `@next-model/graphql-api` — turns any next-model `Model` into typeDefs + resolvers with 6 default CRUD operations (list/get/count/create/update/delete), per-operation auth hooks, and per-row response mapping. Use when triggers like "expose model over GraphQL", "GraphQL CRUD", or "graphql-http" appear, or when wiring a Model into Apollo/Yoga/graphql-http.
SQL connector for `@next-model/core` backed by Knex 3, supporting sqlite3, Postgres, MySQL, MariaDB, Oracle, and MSSQL through any Knex client. Triggers include "Knex connector", "multi-dialect", "Knex pool", and "schema migrations through Knex" — reach for this when you want one connector that targets multiple SQL dialects through Knex rather than a native single-dialect connector.
Use `@next-model/local-storage-connector` to back a `@next-model/core` Model with the browser's `localStorage` (or any `Storage`-shaped object). Inherits from `MemoryConnector`, so all in-memory query semantics carry over verbatim — only persistence and id management differ. Triggers include "browser persistence", "offline-first", "client-side ORM", and "localStorage adapter".