feat(cli): expose build/deploy internals via trigger.dev/internal

Mirror the pattern @trigger.dev/build already uses: a dedicated `./internal`
subpath export for downstream tooling that wants to drive the build / deploy
pipeline programmatically without going through the `trigger` CLI binary.

Adds packages/cli-v3/src/internal.ts re-exporting:

  - loadConfig (trigger.config.ts loader)
  - buildWorker + BuildWorkerOptions (esbuild bundling)
  - buildImage + BuildImageOptions + BuildImageResults (docker buildx orchestration)
  - generateContainerfile + parseGenerateOptions + GenerateContainerfileOptions (Containerfile templating)
  - CliApiClient (typed wrapper around the deploy / register / finalize endpoints)

These modules already existed; this commit just makes them addressable from
outside the CLI package. Also widens the visibility of three buildImage result
types (BuildImageSuccess, BuildImageFailure, BuildImageResults) from
file-private to exported so consumers can statically discriminate the result
union.

No behavior change. The CLI binary continues to import the same modules
internally; nothing on the runtime path is affected.

Co-authored-by: Cursor <cursoragent@cursor.com>

Author: ConProgramming

packages/cli-v3/package.json

@@ -45,7 +45,8 @@
     ],
     "exports": {
       "./package.json": "./package.json",
-      ".": "./src/index.ts"
+      ".": "./src/index.ts",
+      "./internal": "./src/internal.ts"
     }
   },
   "devDependencies": {
@@ -159,6 +160,12 @@
         "types": "./dist/esm/index.d.ts",
         "default": "./dist/esm/index.js"
       }
+    },
+    "./internal": {
+      "import": {
+        "types": "./dist/esm/internal.d.ts",
+        "default": "./dist/esm/internal.js"
+      }
     }
   }
 }

packages/cli-v3/src/deploy/buildImage.ts

@@ -182,20 +182,20 @@ export interface DepotBuildImageOptions {
   onLog?: (log: string) => void;
 }
 
-type BuildImageSuccess = {
+export type BuildImageSuccess = {
   ok: true;
   imageSizeBytes: number;
   logs: string;
   digest?: string;
 };
 
-type BuildImageFailure = {
+export type BuildImageFailure = {
   ok: false;
   error: string;
   logs: string;
 };
 
-type BuildImageResults = BuildImageSuccess | BuildImageFailure;
+export type BuildImageResults = BuildImageSuccess | BuildImageFailure;
 
 async function remoteBuildImage(options: DepotBuildImageOptions): Promise<BuildImageResults> {
   const buildArgs = Object.entries(options.buildEnvVars || {})

packages/cli-v3/src/internal.ts

@@ -0,0 +1,20 @@
+// Public API surface for downstream tooling that wants to drive the
+// build / deploy pipeline programmatically without going through the
+// `trigger` CLI binary.
+//
+// Mirrors the pattern used by `@trigger.dev/build`'s `./internal` subpath:
+// the modules exported here are stable enough to be consumed by adjacent
+// packages, but they sit *below* the documented CLI command surface, so
+// consumers should pin to a specific version of this package.
+
+export { loadConfig } from "./config.js";
+export { buildWorker, type BuildWorkerOptions } from "./build/buildWorker.js";
+export {
+  buildImage,
+  generateContainerfile,
+  parseGenerateOptions,
+  type BuildImageOptions,
+  type BuildImageResults,
+  type GenerateContainerfileOptions,
+} from "./deploy/buildImage.js";
+export { CliApiClient } from "./apiClient.js";