bug: SDK fails in Supabase Edge (Deno) runtime when calling task.trigger()

[isshaddad]

Provide environment information

trigger v4.4.1 but also happens with previous versions

Describe the bug

When triggering a task from a Supabase Edge Function using tasks.trigger() (or task.trigger()), the runtime throws:

TypeError: Cannot read properties of undefined (reading 'toString')
at @bugsnag/cuid (fingerprint.mjs).

This only occurs when the SDK is used to trigger; it does not occur when triggering via the REST API (POST to https://api.trigger.dev/api/v1/tasks/<taskId>/trigger).

Expected: Task triggers successfully from the Edge Function using the SDK.

Actual: Runtime error from a dependency that expects Node-style APIs not available in the Supabase Edge (Deno) runtime. Treating as environment compatibility issue; workaround is to use the Tasks API with fetch instead of the SDK (documented in the Supabase Edge Functions guide).

Reproduction repo

n/a

To reproduce

1. Follow Triggering tasks from Supabase edge functions.
2. In the edge function, use tasks.trigger() (or task.trigger()) with the SDK, e.g. import { tasks } from "@trigger.dev/sdk/v3".
3. Deploy the edge function and invoke it (e.g. hit the function URL or trigger via a DB webhook).
4. Observe runtime error: TypeError: Cannot read properties of undefined (reading 'toString') at @bugsnag/cuid fingerprint.mjs.

Workaround: trigger via the Tasks API with fetch instead of the SDK.

Additional information

No response

[muhaimincs]

Same goes with npm:@trigger.dev/sdk@latest/v3. No luck. Is there any mapping or different path?