CodeVetter · Repo Unpack · Extension points
strapi/strapi
Extensions are intended to enter through factories, plugin contracts, registries, and lifecycle hooks. Backend and browser plugins have separate registration interfaces. Document middleware, provider capabilities, GraphQL extension configuration, and MCP definitions offer additional integration boundaries. Several APIs enforce registration timing or preserve default behavior through explicit fallback logic.
- createCoreController and createCoreService accept objects or callbacks receiving {strapi}, fill missing methods from defaults, and install base implementations as prototypes. createCoreRouter supports prefix, per-action config, only/except filtering, and route type selection.
- Backend plugins can provide register/bootstrap/destroy, configuration defaults/validation, routes, controllers, services, policies, middleware, and content types. Application extensions overlay plugin schemas and may transform the loaded plugin through strapi-server.js.
- The registries provider installs controllers/services/modules/plugins/custom-fields/APIs and sanitizer/validator registries. It creates beforeSync/afterSync hooks, while Strapi invokes application lifecycle functions with {strapi}.
- strapi.documents.use registers Document Service middleware around cached per-content-type repositories. The wrapper excludes updateComponents and omitComponentData from normal middleware interception.
- Browser plugins register through StrapiApp, adding reducers, menu/settings links, routes, widgets, and hooks. Plugin register runs before custom register; Content Manager demonstrates adding its reducer and lazy route subtree.
- Upload providers may implement uploadStream or upload, replaceStream or replace, with delete-then-upload fallback when replacement capabilities are absent. Email providers expose init(options, settings) returning send and optional verification/lifecycle/capability methods.
- GraphQL extension.use accepts configuration objects or factories receiving strapi, nexus, and typeRegistry. generate combines type definitions, Nexus types/plugins, resolvers, and resolver configuration, alongside a shadowCRUD manager.
- MCP exposes tool/prompt/resource definition registries but rejects registration once status leaves idle. CLI extensions enter the commands factory array, while authentication strategies register per route type and may provide a verify function.