Why do you want to contribute?
I'd like to fix #4782 — the three @trigger.dev/sdk type utilities the docs tell people to import, which no longer compile.
I've already diagnosed it. packages/trigger-sdk/src/v3/prompt.ts exports PromptHandle, PromptIdentifier and PromptVariables, and prompts.ts re-exports them — but v3/index.ts only carries them through export * as prompts from "./prompts.js". So they ship, and they're reachable as prompts.PromptHandle, but the named import documented at https://trigger.dev/docs/ai/prompts cannot resolve.
Reproduced against the published @trigger.dev/sdk@4.5.12 using the exact snippet from that page:
sample.ts(1,15): error TS2305: Module '"@trigger.dev/sdk"' has no exported member 'PromptHandle'.
sample.ts(1,29): error TS2305: Module '"@trigger.dev/sdk"' has no exported member 'PromptIdentifier'.
sample.ts(1,47): error TS2305: Module '"@trigger.dev/sdk"' has no exported member 'PromptVariables'.
Confirmed the types themselves are fine — the same snippet written as prompts.PromptHandle type-checks clean, so this is a missing re-export rather than a docs error or a removed API.
Adding the named type exports to the v3 barrel makes the documented snippet compile. I verified that by appending the export line to the shipped index.d.ts in node_modules and re-running the same check: three errors before, zero after.
The change I'd open is one line in packages/trigger-sdk/src/v3/index.ts, plus a patch changeset. Happy to scope it to exactly the three symbols the docs name and leave PromptOptions/ResolvedPrompt/AnyPromptHandle behind the namespace, or export the full set — whichever you prefer.
Prior contributions or relevant experience
https://github.com/painbaba
Recent work, all open and in the same area — browser/agent infrastructure in TypeScript:
- steel-dev/steel-browser#353 — implemented the self-hosted session
timeout the SDKs already exposed; the server accepted the field, always reported timeout: 0, and never released the session. Added the auto-release with a guard against a stale timer releasing a replaced session, plus unit coverage.
- steel-dev/steel-browser#354 — DevTools inspector broke under
USE_SSL; the scheme-strip no-ops on wss:. Also switched the query parameter, since the frontend derives its protocol from the parameter name and would otherwise open an insecure socket and get blocked as mixed content.
- steel-dev/steel-browser#355 — session viewer had no Router mounted, so
useParams() always returned undefined and every URL rendered sessions[0]. Verified with a before/after browser measurement.
I mostly build browser-driving agents, so I'm in SDK and CDP code daily.
Why do you want to contribute?
I'd like to fix #4782 — the three
@trigger.dev/sdktype utilities the docs tell people to import, which no longer compile.I've already diagnosed it.
packages/trigger-sdk/src/v3/prompt.tsexportsPromptHandle,PromptIdentifierandPromptVariables, andprompts.tsre-exports them — butv3/index.tsonly carries them throughexport * as prompts from "./prompts.js". So they ship, and they're reachable asprompts.PromptHandle, but the named import documented at https://trigger.dev/docs/ai/prompts cannot resolve.Reproduced against the published
@trigger.dev/sdk@4.5.12using the exact snippet from that page:Confirmed the types themselves are fine — the same snippet written as
prompts.PromptHandletype-checks clean, so this is a missing re-export rather than a docs error or a removed API.Adding the named type exports to the
v3barrel makes the documented snippet compile. I verified that by appending the export line to the shippedindex.d.tsinnode_modulesand re-running the same check: three errors before, zero after.The change I'd open is one line in
packages/trigger-sdk/src/v3/index.ts, plus a patch changeset. Happy to scope it to exactly the three symbols the docs name and leavePromptOptions/ResolvedPrompt/AnyPromptHandlebehind the namespace, or export the full set — whichever you prefer.Prior contributions or relevant experience
https://github.com/painbaba
Recent work, all open and in the same area — browser/agent infrastructure in TypeScript:
timeoutthe SDKs already exposed; the server accepted the field, always reportedtimeout: 0, and never released the session. Added the auto-release with a guard against a stale timer releasing a replaced session, plus unit coverage.USE_SSL; the scheme-strip no-ops onwss:. Also switched the query parameter, since the frontend derives its protocol from the parameter name and would otherwise open an insecure socket and get blocked as mixed content.useParams()always returned undefined and every URL renderedsessions[0]. Verified with a before/after browser measurement.I mostly build browser-driving agents, so I'm in SDK and CDP code daily.