Packages

@vercel/node

32.0.0 · 18 Nov 2026Apache-2.06.3M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/node From 5.7.16 to 5.7.17

1 release in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 5.7.16Newest 5.x5.10.2Latest32.0.0
  1. 5.7.16yours
  2. 5.7.17target
0
changes to make
0
advisories fixed
0
new
1
fix

Release by release

  1. 5.7.17

    10 May 20261 fix
    • Fixed

      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.

1 internal line (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.