Anyone have a working SvelteKit + Trigger.dev v3 setup?

[perostlin]

Hello,

Does anyone have a project setup using SvelteKit + Trigger.dev v2?

I’m having some issues when triggering a task from a server endpoint, can’t use SvelteKit’s $env inside the task and process.env seem to take the values from my .env file.

Any ideas?💡

[KeuqS]

That behavior is expected because the SvelteKit server and a Trigger task run in different runtimes. SvelteKit's $env modules are provided by the SvelteKit/Vite build and are not automatically available inside the Trigger worker. Inside the task, process.env comes from the Trigger environment (or the local .env used by the Trigger CLI), not from SvelteKit's env loader.

Also, the question is using Trigger.dev v2 terminology. New v2 projects are no longer created, so the supported path is v3 or newer. For a v3 setup:

• Keep secrets in the Trigger.dev DEV/STAGING/PROD environment variables (and a local .env for development).
• Read them with process.env inside the task.
• Trigger the task from a SvelteKit server endpoint, never from browser code.
• Pass only non-secret request data in the task payload; do not forward private env values to the client.
• If the value belongs to the SvelteKit app rather than the worker, resolve it in the server endpoint and pass the safe value explicitly.

If you need SvelteKit functions inside tasks, the community vite-plugin-triggerkit package provides SvelteKit/Vite integration and hot reload. It does not replace Trigger's own task environment variables.

References:

• v2 projects were replaced by v3: https://trigger.dev/changelog/improved-create-integration-docs
• v3 environment variable handling: https://trigger.dev/changelog/env-vars-sdk
• SvelteKit integration: https://trigger.dev/changelog/sveltekit-plugin