Prerequisites
- A Veryfront project with
veryfront.config.ts. - For a first-party extension: the matching package installed.
- For a local extension: a folder under
extensions/with a default-exported factory (see Extension authoring).
Enable an extension
Add extension factories toveryfront.config.ts:
veryfront.config.ts to force reload during development.
First-party extension areas
| Area | Example package | Contract family |
|---|---|---|
| Auth | @veryfront/ext-auth-jwt | AuthProvider |
| Cache | @veryfront/ext-cache-redis | CacheStore |
| Content | @veryfront/ext-content-mdx | content parsing |
| CSS | @veryfront/ext-css-tailwind | CSS processing |
| Database | @veryfront/ext-db-sqlite | database access |
| LLM | @veryfront/ext-llm-openai | model providers |
| Observability | @veryfront/ext-observability-opentelemetry | telemetry |
| Parser | @veryfront/ext-parser-babel | parsing |
| Sandbox | @veryfront/ext-sandbox-shell-tools | sandbox tools |
| Schema | @veryfront/ext-schema-zod | schema validation |
Verify it worked
Restartveryfront dev after editing veryfront.config.ts:
- The dev log should print a setup line for each loaded extension.
- Any contract the extension provides should now be resolvable through the
matching consumer (for example, a
CacheStoreextension lets cache-aware code skip its local fallback). - If the factory throws during setup, the dev server prints the setup error with the extension name. Fix the error and reload.