Files
nicktrn a9f756b260 chore: move reference projects to their own repo (#3812)
The reference/example projects (`references/`) now live in their own
repo, https://github.com/triggerdotdev/references, so their heavy,
frequently-changing dependencies are no longer part of this repo's
lockfile and tooling. This removes them here and repoints everything
that referenced them.

- Deletes `references/`; updates the pnpm workspace + lockfile.
- Clears the references-only CI rules and `.vscode` configs.
- Repoints the docs (contributor/agent + one public page) to the new
repo.
- `seed.mts` keeps the local-dev projects (hello-world, d3-chat,
realtime-streams).
2026-06-02 22:19:28 +01:00

957 B

Trigger.dev SDK

@trigger.dev/sdk - the main customer-facing SDK for writing background tasks.

Import Rules

Always import from @trigger.dev/sdk. Never use @trigger.dev/sdk/v3 (deprecated path alias).

Key Exports

  • task - Define a background task
  • schedules.task - Define a scheduled (cron) task
  • batch - Batch trigger operations
  • runs - Run management and polling
  • wait - Wait for events, delays, or other tasks
  • retry - Retry utilities
  • queue - Queue configuration
  • metadata - Run metadata access
  • logger - Structured logging

When Adding Features

  1. Implement the feature in the SDK
  2. Test with the hello-world project in the triggerdotdev/references repo
  3. Docs updates (docs/) are usually done in a separate PR

Do NOT update rules/ or .claude/skills/trigger-dev-tasks/ unless explicitly asked. These are maintained in separate dedicated passes.