Hi — requesting a vouch so I can open a PR, per CONTRIBUTING.
What I'd like to work on
#4812 — the TypeScript sample on /docs/ai/prompts doesn't compile. I've already reproduced and confirmed it against @trigger.dev/sdk@4.5.13 before asking, so the PR would be ready to go.
The documented import fails with three TS2305s:
import type { PromptHandle, PromptIdentifier, PromptVariables } from "@trigger.dev/sdk";
error TS2305: Module '"@trigger.dev/sdk"' has no exported member 'PromptHandle'.
error TS2305: Module '"@trigger.dev/sdk"' has no exported member 'PromptIdentifier'.
error TS2305: Module '"@trigger.dev/sdk"' has no exported member 'PromptVariables'.
The types are real, they're just reachable only through the prompts namespace (v3/index.d.ts has export * as prompts from "./prompts.js"). I checked the alternatives rather than assuming:
| form |
result |
import type { PromptHandle } from "@trigger.dev/sdk" |
fails (as documented) |
import { prompts } then prompts.PromptHandle |
compiles |
import type { PromptHandle } from "@trigger.dev/sdk/v3" |
fails |
So the doc change is to the namespace form. Scope is docs only, one issue, no SDK change — matching the one-issue-per-PR rule.
Background
Recent contributions elsewhere: a merged PR to KalyteraSystems/IPCamLapse, plus open PRs to apache/airflow (#72163, adding an airflowctl tasks state command), secdev/scapy (#5117, RFC 791 IP timestamp option), and pymovements (#1705). I test changes locally before submitting rather than relying on them looking right.
Disclosure: I use AI assistance (Claude Code) when working, and I verify everything it produces by running it — the type-check results above are actual output, not asserted.
Happy to pick up something else instead if #4812 is already spoken for or too small to be worth a vouch.
Hi — requesting a vouch so I can open a PR, per CONTRIBUTING.
What I'd like to work on
#4812 — the TypeScript sample on
/docs/ai/promptsdoesn't compile. I've already reproduced and confirmed it against@trigger.dev/sdk@4.5.13before asking, so the PR would be ready to go.The documented import fails with three
TS2305s:The types are real, they're just reachable only through the
promptsnamespace (v3/index.d.tshasexport * as prompts from "./prompts.js"). I checked the alternatives rather than assuming:import type { PromptHandle } from "@trigger.dev/sdk"import { prompts }thenprompts.PromptHandleimport type { PromptHandle } from "@trigger.dev/sdk/v3"So the doc change is to the namespace form. Scope is docs only, one issue, no SDK change — matching the one-issue-per-PR rule.
Background
Recent contributions elsewhere: a merged PR to KalyteraSystems/IPCamLapse, plus open PRs to apache/airflow (#72163, adding an
airflowctl tasks statecommand), secdev/scapy (#5117, RFC 791 IP timestamp option), and pymovements (#1705). I test changes locally before submitting rather than relying on them looking right.Disclosure: I use AI assistance (Claude Code) when working, and I verify everything it produces by running it — the type-check results above are actual output, not asserted.
Happy to pick up something else instead if #4812 is already spoken for or too small to be worth a vouch.