@boboddy/sdk 0.4.3 → 0.5.1

package/dist/push/collect-definitions.d.ts

@@ -8,6 +8,21 @@ export type CollectedDefinitions = {
     /** Present only when `default-pipeline-assignment.ts` exists in the directory. */
     readonly defaultPipelineAssignment: DefaultPipelineAssignmentSpec | null;
 };
+/**
+ * One source file that failed to produce a pipeline —
+ * `collectDefinitionsFromDirectoryTolerant`'s per-file counterpart to a
+ * `collectDefinitionsFromDirectory` throw. `key` is a best-effort
+ * identifier: the file's own basename (no extension), since a failure can
+ * happen before `definePipeline()` ever runs and assigns the pipeline its
+ * real `key`.
+ */
+export type BrokenPipeline = {
+    readonly key: string;
+    readonly message: string;
+};
+export type TolerantCollectedDefinitions = CollectedDefinitions & {
+    readonly brokenPipelines: readonly BrokenPipeline[];
+};
 /**
  * Imports every `.ts`/`.js` file in `dir` (except the push script itself and
  * `default-pipeline-assignment.ts`) and collects the pipeline and step
@@ -16,6 +31,30 @@ export type CollectedDefinitions = {
  *
  * Designed to run on the user's native runtime (bun, node-with-tsx, deno), NOT
  * inside a `bun --compile`'d binary — that runtime can't resolve scoped package
- * `exports` field remappings from external user files.
+ * `exports` field remappings from external user files. `boboddy pipelines
+ * studio` works around this for its own compiled binary by never calling this
+ * function in-process: `collectDefinitionsViaSubprocess` (in
+ * `packages/worker/src/pipelines/pipeline-studio/infra/collect-definitions-via-subprocess.ts`)
+ * spawns a real bun/tsx/deno subprocess that calls this exact function from
+ * outside the compiled binary. Calling it directly, in-process, from inside a
+ * compiled binary is still unsupported.
+ *
+ * Throws on the first bad file — a syntax error, a `definePipeline()`-time
+ * validation failure, an unresolvable `codeStep` entrypoint — aborting the
+ * whole collection. That's the right behavior for `boboddy pipelines push`
+ * (this function's only real caller besides its own tests): pushing a
+ * partially-collected directory would be worse than refusing to push at all.
+ * `boboddy pipelines studio` wants the opposite trade-off — see
+ * `collectDefinitionsFromDirectoryTolerant` below.
  */
 export declare function collectDefinitionsFromDirectory(dir: string): Promise<CollectedDefinitions>;
+/**
+ * `collectDefinitionsFromDirectory`'s tolerant sibling, built for `boboddy
+ * pipelines studio`: one file failing to import or compile (a syntax error,
+ * an `assertTargetExists`-style `definePipeline()` throw, an unresolvable
+ * `codeStep` entrypoint, ...) is recorded as a `BrokenPipeline` entry instead
+ * of aborting collection — every *other* file's pipeline still comes back
+ * usable, so one bad edit in the builder directory doesn't blank the whole
+ * designer (see `compute-studio-snapshot.ts`).
+ */
+export declare function collectDefinitionsFromDirectoryTolerant(dir: string): Promise<TolerantCollectedDefinitions>;

package/dist/push/index.d.ts

@@ -1,4 +1,4 @@
-export { collectDefinitionsFromDirectory } from "./collect-definitions";
-export type { CollectedDefinitions } from "./collect-definitions";
+export { collectDefinitionsFromDirectory, collectDefinitionsFromDirectoryTolerant, } from "./collect-definitions";
+export type { BrokenPipeline, CollectedDefinitions, TolerantCollectedDefinitions, } from "./collect-definitions";
 export { pushFromDirectory } from "./push-from-directory";
 export type { PushFromDirectoryOptions, PushFromDirectoryResult, } from "./push-from-directory";