How to get setup and deploy Jobs for your SvelteKit project
To begin, install the necessary packages in your Sveltekit project directory. You can choose one of the following package managers:
To locate your development API key, login to the Trigger.dev
dashboard and select the Project you want to
connect to. Then click on the Environments & API Keys tab in the left menu.
You can copy your development API Key from the field at the top of this page.
(Your development key will start with tr_dev_
).
Create a .env
file at the root of your project and include your Trigger API key and URL like this:
Replace ENTER_YOUR_DEVELOPMENT_API_KEY_HERE
with the actual API key obtained from the previous step.
You will have type errors for your environment variables unless you run this command:
Create a file at <root>/src/trigger.ts
or <root>/trigger.ts
depending on whether you're using the src
directory or not. <root>
represents the root directory of your project.
Next, add the following code to the file which creates and exports a new TriggerClient
:
Replace "my-app" with an appropriate identifier for your project.
To establish an API route for interacting with Trigger.dev, follow these steps based on your project's file type and structure
Create a new file named +server.(ts/js)
within the src/routes/api/trigger
directory, and add the following code:
jobs
alongside your src
directoryjobs
folder, add two files named example.(ts/js)
and index.(ts/js)
.You can define more job definitions by creating additional files in the jobs
folder and exporting them in the src/jobs/index
file.
For example, in index.(ts/js)
, you can export other job files like this:
package.json
Inside the package.json
file, add the following configuration under the root object:
Your package.json
file might look something like this:
Replace "my-app" with the appropriate identifier you used during the step for creating the Trigger Client.
Run your Sveltekit app locally. You need to use the --host
flag to allow the Trigger.dev CLI to connect to your app.
For example:
In a separate terminal window or tab run:
You can optionally pass the port if you're not running on 3000 by adding
--port 5173
to the end
You can optionally pass the hostname if you're not running on localhost by adding
--hostname <host>
. Example, in case your Sveltekit app is running on 0.0.0.0: --hostname 0.0.0.0
.