Background
Users of the TypeScript task SDK currently have to run esbuild by hand and hand-write the airflow-metadata.yaml sidecar next to the bundle. Folding metadata generation into the build tooling was deferred to a follow-up in #68548 and #69079.
What needs to happen
- Add a
ts pack (or similar) CLI tool that bundles TypeScript handlers into a single bundle.mjs via esbuild.
- Auto-generate
airflow-metadata.yaml from the handler registry.
- Combine the
.mjs and metadata into a single artifact to avoid drift between the two files.
Acceptance criteria
- One command produces a deployable TypeScript bundle with correct metadata.
- No hand-written metadata sidecar is needed.
Context
Background
Users of the TypeScript task SDK currently have to run esbuild by hand and hand-write the
airflow-metadata.yamlsidecar next to the bundle. Folding metadata generation into the build tooling was deferred to a follow-up in #68548 and #69079.What needs to happen
ts pack(or similar) CLI tool that bundles TypeScript handlers into a singlebundle.mjsvia esbuild.airflow-metadata.yamlfrom the handler registry..mjsand metadata into a single artifact to avoid drift between the two files.Acceptance criteria
Context