unstale

npm / @vercel/functions

@vercel/functions

What changed in @vercel/functions 3, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-21.

1 breaking5 new APIs and options2 behavior and defaults4 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@unstale/cli 0.2.1 on npm

@vercel/functions 312 changes

Breaking changes 1

  • InMemoryCache now JSON-serializes values on set and deserializes them on get, matching RuntimeCache and making behavior consistent when switching cache implementations.

    3.4.1release notes

New APIs and options 5

  • Adds a maxPayload option, defaulting to 256 KiB, to configure the maximum WebSocket payload.

    3.7.2release notes

  • Adds the experimental_upgradeWebSocket() API.

    3.7.0release notes

  • Introduces the Vercel AddCacheTag API, addCacheTag.

    3.3.0release notes

  • Adds an API to dangerously delete by source image.

    3.2.0release notes

  • Adds an API to invalidate by source image.

    3.2.0release notes

Behavior and default changes 2

  • ws is now an optional peer dependency.

    3.7.1release notes

  • getCache().set() defaults options.name to the provided key when omitted, giving cache entries a human-readable label in o11y; pass name: '' to suppress this and use the hashed key.

    3.6.0release notes

Fixes and other changes 4

  • URL encoding of cache tags is reverted, restoring the previous behavior.

    3.4.3release notes

  • Cache tags are URL encoded before being sent to the cache API, so tags containing special characters are handled correctly when setting cache entries or expiring tags.

    3.4.0release notes

  • Fixes TimeoutNegativeWarning in Node.js v24 when a process runs longer than 15 minutes by ensuring a minimum wait time of 100ms.

    3.3.6release notes

  • Fixes addCacheTag(), which was previously a no-op.

    3.3.2release notes