Trigger Adapters Development

This skill helps you work with the trigger-adapters repository, a Turborepo monorepo containing framework-specific adapters for Trigger.dev SDK integration. The project uses Bun as the package manager and Biome for linting/formatting.

Repository Structure

The monorepo contains:

- `/src/core.ts` - Core trigger function wrapping `@trigger.dev/sdk`

- `/src/express.ts` - Express.js adapter

- `/src/hono.ts` - Hono adapter

- `/src/nextjs.ts` - Next.js adapter

Development Workflow

Step 1: Install Dependencies

From the repository root:

```bash

bun install

```

Step 2: Development Commands

**Build all packages:**

```bash

bun run build

or

turbo run build

```

**Development mode (all packages with watch):**

```bash

bun run dev

or

turbo run dev

```

**Lint and format with Biome:**

```bash

Check for issues

bun run check

Auto-fix issues

bun run check:write

```

**Type checking across all packages:**

```bash

bun run check-types

or

turbo run check-types

```

**Target specific packages:**

```bash

turbo run build --filter=trigger-adapters

turbo run dev --filter=www

```

Step 3: Working with the Adapters Package

Navigate to the package directory:

```bash

cd packages/trigger-adapters

```

**Build the library (uses tsdown):**

```bash

bun run build

```

**Development mode with watch:**

```bash

bun run dev

```

**Run tests with Vitest:**

```bash

bun run test

```

**Type checking:**

```bash

bun run typecheck

```

**Release new version (uses bumpp):**

```bash

bun run release

```

Step 4: Working with Documentation

Navigate to documentation site:

```bash

cd apps/www

```

**Start dev server:**

```bash

bun run dev

```

**Build documentation:**

```bash

bun run build

```

**Preview built documentation:**

```bash

bun run preview

```

Code Architecture

Adapter Pattern

Each adapter follows this structure:

1. **Core Function** (`core.ts`) - Wraps the Trigger.dev SDK's `tasks.trigger()` function

2. **Framework Adapters** - Each exports a `handler()` function that:

- Extracts the task ID from request parameters (typically `params.id`)

- Extracts payload from request body

- Calls the core `trigger()` function

- Returns result in framework-appropriate format

Build System

Code Style

Testing

Build Outputs

Important Notes