@vercel/build-utils 13.22.0 → 13.22.1

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # @vercel/build-utils
 
+## 13.22.1
+
+### Patch Changes
+
+- f0d7d32: Disable response streaming for lambdas with `awsLambdaHandler` set inside `getLambdaSupportsStreaming`. This closes a gap where non-Node builders (e.g. `@vercel/redwood`) constructed `NodejsLambda` with `awsLambdaHandler` but no explicit `supportsResponseStreaming`, causing `finalizeLambda` to silently flip streaming on for AWS custom handlers. With the gate now enforced centrally in `finalizeLambda`, the equivalent `@vercel/node` build-time check from #16266 is consolidated away — all builders go through the same gate.
+
 ## 13.22.0
 
 ### Minor Changes

package/dist/index.js

@@ -32604,6 +32604,9 @@ function getLambdaEnvironment(lambda, buffer, options) {
 
 // src/process-serverless/get-lambda-supports-streaming.ts
 async function getLambdaSupportsStreaming(lambda, forceStreamingRuntime) {
+  if (lambda.awsLambdaHandler) {
+    return { supportsStreaming: false };
+  }
   if (forceStreamingRuntime) {
     return { supportsStreaming: true };
   }

package/dist/process-serverless/get-lambda-supports-streaming.d.ts

@@ -1,4 +1,5 @@
 interface LambdaLike {
+    awsLambdaHandler?: string;
     handler: string;
     launcherType?: string;
     runtime: string;
@@ -12,9 +13,17 @@ export interface SupportsStreamingResult {
     };
 }
 /**
- * Determines if a Lambda should have streaming enabled. If
- * `forceStreamingRuntime` is true, streaming is always enabled. If the
- * setting is defined it will be honored. Enabled by default for Node.js.
+ * Determines if a Lambda should have streaming enabled.
+ *
+ * AWS custom handlers cannot stream — the handler contract returns a
+ * response object, not a stream — so they always resolve to `false`,
+ * even when `forceStreamingRuntime` is set. This mirrors
+ * `deserializeLambda`, which also refuses to force streaming on lambdas
+ * with an `awsLambdaHandler` set.
+ *
+ * Otherwise: if `forceStreamingRuntime` is true, streaming is always
+ * enabled. If the setting is defined it will be honored. Enabled by
+ * default for Node.js.
  */
 export declare function getLambdaSupportsStreaming(lambda: LambdaLike, forceStreamingRuntime: boolean): Promise<SupportsStreamingResult>;
 export {};

package/dist/process-serverless/get-lambda-supports-streaming.js

@@ -22,6 +22,9 @@ __export(get_lambda_supports_streaming_exports, {
 });
 module.exports = __toCommonJS(get_lambda_supports_streaming_exports);
 async function getLambdaSupportsStreaming(lambda, forceStreamingRuntime) {
+  if (lambda.awsLambdaHandler) {
+    return { supportsStreaming: false };
+  }
   if (forceStreamingRuntime) {
     return { supportsStreaming: true };
   }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/build-utils",
-  "version": "13.22.0",
+  "version": "13.22.1",
   "license": "Apache-2.0",
   "main": "./dist/index.js",
   "types": "./dist/index.d.js",
@@ -53,8 +53,8 @@
     "smol-toml": "1.5.2",
     "vitest": "2.0.1",
     "yazl": "2.5.1",
-    "@vercel/routing-utils": "6.2.0",
-    "@vercel/error-utils": "2.1.0"
+    "@vercel/error-utils": "2.1.0",
+    "@vercel/routing-utils": "6.2.0"
   },
   "scripts": {
     "build": "node build.mjs",