@hyperframes/aws-lambda 0.6.80 → 0.6.81

package/dist/sdk/validateConfig.d.ts

@@ -1,56 +1,31 @@
 /**
- * Client-side validation of `SerializableDistributedRenderConfig` so the
- * SDK fails on shape errors with a typed `InvalidConfigError` *before* a
- * Step Functions execution starts.
+ * Client-side validation for the AWS Lambda adapter.
  *
- * The producer's `plan` stage validates the same fields server-side, but a
- * caller staring at "ExecutionFailed: BROWSER_GPU_NOT_SOFTWARE" five
- * minutes after StartExecution has to dig through Step Functions history
- * to learn that the renderToLambda call passed an unsupported format.
- * Catching the obvious mistakes locally turns that wait into a synchronous
- * throw.
- *
- * The check is deliberately narrow — it covers the *shape* errors any
- * caller could have surfaced with `tsc` if they passed a literal, plus
- * the `force-hdr` rejection (HDR mp4 isn't supported in distributed
- * mode). webm was previously rejected here too; v0.7+ supports it via
- * closed-GOP concat-copy. Anything deeper (font availability, plan
- * size cap, GPU mode at runtime) needs the actual planner.
- */
-import type { SerializableDistributedRenderConfig } from "../events.js";
-/** Thrown for any client-side `SerializableDistributedRenderConfig` violation. */
-export declare class InvalidConfigError extends Error {
-    readonly name = "InvalidConfigError";
-    /** Dotted JSON-pointer-ish path to the offending field, e.g. `config.fps`. */
-    readonly field: string;
-    constructor(field: string, message: string);
-}
-/**
- * Throw an `InvalidConfigError` if `config` is not a valid
- * `SerializableDistributedRenderConfig`. Returns the same reference on
- * success so the call site reads:
- *
- *     const validated = validateDistributedRenderConfig(input);
+ * The cloud-agnostic config-shape validation (`validateDistributedRenderConfig`,
+ * `validateVariablesPayload`, `InvalidConfigError`) lives in
+ * `@hyperframes/producer/distributed` and is shared with the other adapters.
+ * This module re-exports those and adds the one piece specific to Step
+ * Functions: the 256 KiB Standard-workflow execution-input size cap.
  */
-export declare function validateDistributedRenderConfig(config: SerializableDistributedRenderConfig): SerializableDistributedRenderConfig;
+export { InvalidConfigError, validateDistributedRenderConfig, validateVariablesPayload, } from "@hyperframes/producer/distributed";
 /**
- * Hard cap on Step Functions Standard workflow execution input — 256 KiB
- * per the AWS limits page. Express workflows cap at 32 KiB; the render
- * stack runs Standard for execution-history visibility, so the larger
- * limit applies. The cap is on the entire serialized input, not just the
- * variables, because users hit it at the wire boundary regardless of
- * which field caused the bloat.
+ * Hard cap on Step Functions Standard workflow execution input — 256 KiB per
+ * the AWS limits page. Express workflows cap at 32 KiB; the render stack runs
+ * Standard for execution-history visibility, so the larger limit applies. The
+ * cap is on the entire serialized input, not just the variables, because
+ * users hit it at the wire boundary regardless of which field caused the
+ * bloat.
  *
  * Specific to Step Functions Standard. Other workflow runtimes (Temporal,
- * Express SFN, raw Lambda invoke) have different caps; this constant
- * shouldn't be reused for those without confirming the limit.
+ * Express SFN, Cloud Workflows, raw Lambda invoke) have different caps; don't
+ * reuse this constant for those without confirming the limit.
  */
 export declare const MAX_STEP_FUNCTIONS_INPUT_BYTES: number;
 /**
- * Validate that the serialized Step Functions execution input fits inside
- * the 256 KiB Standard-workflow cap. Measured in UTF-8 bytes (the format
- * Step Functions uses on the wire) — JS strings count UTF-16 code units,
- * which under-reports for any multi-byte character.
+ * Validate that the serialized Step Functions execution input fits inside the
+ * 256 KiB Standard-workflow cap. Measured in UTF-8 bytes (the format Step
+ * Functions uses on the wire) — JS strings count UTF-16 code units, which
+ * under-reports for any multi-byte character.
  *
  * Throws {@link InvalidConfigError} with a clear message naming the actual
  * byte count, the cap, and a pointer to the "working with large variables"
@@ -59,17 +34,4 @@ export declare const MAX_STEP_FUNCTIONS_INPUT_BYTES: number;
  * execution.
  */
 export declare function validateStepFunctionsInputSize(input: unknown): void;
-/**
- * Validate that `variables` is a plain JSON-safe object — no functions,
- * Symbols, `undefined` leaves, BigInts, non-finite numbers, or non-plain
- * objects (Dates, Maps, Sets, class instances). Rejected values would
- * either round-trip incorrectly through Step Functions (`undefined` is
- * silently dropped by `JSON.stringify`) or throw at the wire boundary
- * (`bigint`), so we surface the offending path synchronously.
- *
- * The check is purely structural — semantic constraints (e.g. "is this
- * variable declared in `data-composition-variables`?") belong to the CLI
- * layer where the project's HTML is on disk.
- */
-export declare function validateVariablesPayload(value: unknown): void;
 //# sourceMappingURL=validateConfig.d.ts.map

package/dist/sdk/validateConfig.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"validateConfig.d.ts","sourceRoot":"","sources":["../../src/sdk/validateConfig.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;GAkBG;AAGH,OAAO,KAAK,EAAE,mCAAmC,EAAE,MAAM,cAAc,CAAC;AAExE,kFAAkF;AAClF,qBAAa,kBAAmB,SAAQ,KAAK;IAG3C,SAAkB,IAAI,wBAAwB;IAC9C,8EAA8E;IAC9E,QAAQ,CAAC,KAAK,EAAE,MAAM,CAAC;gBACX,KAAK,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM;CAI3C;AAmBD;;;;;;GAMG;AACH,wBAAgB,+BAA+B,CAC7C,MAAM,EAAE,mCAAmC,GAC1C,mCAAmC,CAoHrC;AAED;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,8BAA8B,QAAa,CAAC;AAMzD;;;;;;;;;;;GAWG;AAEH,wBAAgB,8BAA8B,CAAC,KAAK,EAAE,OAAO,GAAG,IAAI,CAkCnE;AAED;;;;;;;;;;;GAWG;AACH,wBAAgB,wBAAwB,CAAC,KAAK,EAAE,OAAO,GAAG,IAAI,CAQ7D"}
+{"version":3,"file":"validateConfig.d.ts","sourceRoot":"","sources":["../../src/sdk/validateConfig.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAIH,OAAO,EACL,kBAAkB,EAClB,+BAA+B,EAC/B,wBAAwB,GACzB,MAAM,mCAAmC,CAAC;AAE3C;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,8BAA8B,QAAa,CAAC;AAMzD;;;;;;;;;;;GAWG;AAEH,wBAAgB,8BAA8B,CAAC,KAAK,EAAE,OAAO,GAAG,IAAI,CA6BnE"}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hyperframes/aws-lambda",
-  "version": "0.6.80",
+  "version": "0.6.81",
   "description": "AWS Lambda adapter for HyperFrames distributed rendering — handler, client-side SDK, and CDK construct.",
   "repository": {
     "type": "git",
@@ -45,7 +45,7 @@
     "ffprobe-static": "^3.1.0",
     "puppeteer-core": "^24.39.1",
     "tar": "^7.4.3",
-    "@hyperframes/producer": "^0.6.80"
+    "@hyperframes/producer": "^0.6.81"
   },
   "devDependencies": {
     "@types/aws-lambda": "^8.10.146",