Skip to main content

Documentation Index

Fetch the complete documentation index at: https://veryfront.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

​
Extension lifecycle

The extension lifecycle controls how Veryfront discovers, orders, starts, and stops extension factories.

​
Prerequisites

  • At least one extension installed or local (see Extensions).
  • The dev server running so you can observe setup and teardown logs.

​
Load sequence

discover -> flatten presets -> topological sort -> setup() -> runtime -> teardown()
  1. Discovery finds configured, local, and package-provided extensions.
  2. Presets expand into their child extensions.
  3. Topological sort loads providers before consumers.
  4. setup() runs in sorted order.
  5. teardown() runs in reverse order during shutdown or reload.

​
Presets

Use presets to group extensions that should usually be installed together: 
import type { ExtensionFactory } from "veryfront/extensions";

const webPreset: ExtensionFactory = () => ({
  name: "web-preset",
  version: "1.0.0",
  capabilities: [],
  extends: [
    authExtension(),
    cacheExtension(),
  ],
});

export default webPreset;
Presets are flattened before ordering. Their children are treated as independent extensions for conflict detection and load order.

​
Configuration

Pass configuration through the extension factory: 
extRedis({ url: "redis://localhost:6379", prefix: "myapp:" });
Extensions can also read project config through ctx.config during setup().

​
Development reloads

During development, changes to veryfront.config.ts trigger teardown, rediscovery, and setup. Extensions must release resources in teardown() so reloads do not leak connections, timers, or file handles. Verify reload behavior by adding a temporary log in the extension setup() and teardown() methods, then run: 
veryfront dev
Save veryfront.config.ts. The dev server should run teardown() for the previous extension instance and setup() for the new one.

​
Verify it worked

With the temporary setup()/teardown() logs in place:
  • On veryfront dev startup, every extension prints a setup log line.
  • Save veryfront.config.ts. Each affected extension should print a teardown log line and then a fresh setup log line.
  • On Ctrl+C, every extension prints its final teardown log line.
Remove the temporary logs before publishing the extension.

​
Next