nicktrn
2b586c87a0
* remove dead code * rename managed to shared runtime manager * rename to resolve waitpoint for clarity * add resolver id helper * store and correctly resolve waipoints that come in early * fix ipc message type change * branded type for resolver ids * add fixme comments * remove more unused ipc schemas * fix entitlement validation when client doesn't exist * restore hello world reference workspace imports * runtime manager debug logs * prefix engine run logs * managed run logger accepts nested props * runtime suspendable state and improved logs * require suspendable state for checkpoints, fix snapshot processing queue * add terminal link as cli module so we can more easily patch it * apply cursor patch * add license info * remove terminal-link package and add deprecation notice * remove old patch * remove terminal-link from sdk * rename snapshot module * add cli test tsconfig * add run logger base type * add snapshot manager tests * fix cli builds * improve QUEUED_EXECUTING test * changeset * make testcontainers wait until container has stopped * require unit tests for publishing again * avoid mutation during iteration when resolving pending waitpoints * improve debug logs and make them less noisy * always update poller snapshot id for accurate logs * detach task run process handlers * check for env overrides in a few more places and add verbose logs * log when poller is still executing when we stop it * add supervisor to publish workflow * always print full deploy logs in CI * Revert "avoid mutation during iteration when resolving pending waitpoints" This reverts commit87b0ce1e5b. * disable pre * print prerelease script errors * Revert "disable pre" This reverts commit9403409637. * misc fixes * better debug logs * add snapshots since methods and route * prep for snapshots since * improve deprecated execution detection * update supervisor and schema * properly log http server errors * detect restore after failed snapshot fetch * run and snapshot id can be overridden * fix restore detection * fix deprecation checks, move into snapshot manager * less logs * rename snapshot manager stop * restore detection was moved into snapshot manager * fix notifier logs * make runtime manager status a debug log * no need to attach runtime status twice * findUnique -> findFirst * sort snapshots by created at everywhere
About Trigger.dev
Trigger.dev is an open source platform and SDK which allows you to create long-running background jobs. Write normal async code, deploy, and never hit a timeout.
Key features:
- JavaScript and TypeScript SDK
- No timeouts
- Retries (with exponential backoff)
- Queues and concurrency controls
- Schedules and crons
- Full Observability; logs, live trace views, advanced filtering
- React hooks to interact with the Trigger API from your React app
- Pipe LLM streams straight to your users through the Realtime API
- Trigger tasks and display the run status and metadata anywhere in your app
- Custom alerts, get notified by email, Slack or webhooks
- No infrastructure to manage
- Elastic (scaling)
- Works with your existing tech stack
In your codebase
Create tasks where they belong: in your codebase. Version control, localhost, test and review like you're already used to.
import { task } from "@trigger.dev/sdk/v3";
//1. You need to export each task
export const helloWorld = task({
//2. Use a unique id for each task
id: "hello-world",
//3. The run function is the main function of the task
run: async (payload: { message: string }) => {
//4. You can write code that runs for a long time here, there are no timeouts
console.log(payload.message);
},
});
Deployment
Use our SDK to write tasks in your codebase. There's no infrastructure to manage, your tasks automatically scale and connect to our cloud. Or you can always self-host.
Environments
We support Development, Staging, and Production environments, allowing you to test your tasks before deploying them to production.
Full visibility of every job run
View every task in every run so you can tell exactly what happened. We provide a full trace view of every task run so you can see what happened at every step.
Getting started
The quickest way to get started is to create an account and project in our web app, and follow the instructions in the onboarding. Build and deploy your first task in minutes.
Useful links:
- Quick start - get up and running in minutes
- How it works - understand how Trigger.dev works under the hood
- Guides and examples - walk-through guides and code examples for popular frameworks and use cases
Self-hosting
If you prefer to self-host Trigger.dev, you can follow our self-hosting guide.
We also have a dedicated self-hosting channel in our Discord server for support.
Development
To setup and develop locally or contribute to the open source project, follow our development guide.