This guide will show you how to setup Trigger.dev with Bun
curl -fsSL https://bun.sh/install | bash -s -- bun-v1.1.24
Run the CLI `init` command
/trigger
folder and give you an example task.Run this command in the root of your project to get started:trigger.config.ts
file in the root of your project./trigger
directory./src/trigger
directory with an example task, /src/trigger/example.[ts/js]
.Update example.ts to use Bun
/src/trigger/example.ts
file and replace the contents with the following:Run the CLI `dev` command
dev
command runs a server for your tasks. It watches for changes in your /trigger
directory and communicates with the Trigger.dev platform to register your tasks, perform runs, and send data back and forth.It can also update your @trigger.dev/*
packages to prevent version mismatches and failed deploys. You will always be prompted first.Perform a test run using the dashboard
dev
command spits out various useful URLs. Right now we want to visit the Test page .You should see our Example task in the list , select it. Most tasks have a “payload” which you enter in the JSON editor , but our example task doesn’t need any input.Press the “Run test” button .View your run
register
hook. This means that some libraries that rely on this hook will not work with Bun.