Vercel Functions

Backend & Infra

Develop. Preview. Ship.

Latest: @vercel/static-build@2.11.1325 releases2 common errorsUpdated Jul 30, 2026View on GitHub

Release History

View all versions →

@vercel/static-build@2.11.131 fix

Jul 30, 2026

This patch release ensures that per-function `maxConcurrency` configurations are correctly propagated into build outputs. It also guarantees that each Next.js route with a configured concurrency limit is placed in its own Lambda group.

@vercel/python@6.54.11 fix

Jul 30, 2026

This patch introduces validation for Python queue subscriber topics against build-time introspected subscriptions. The `topics` field is now optional, defaulting to all introspected subscriptions when not provided.

@vercel/passport@1.0.01 feature

Jul 30, 2026

The `@vercel/passport` package has been promoted to a stable 1.0.0 release, indicating a significant milestone for its stability and feature set.

@vercel/node@5.9.3

Jul 30, 2026

This patch release includes updates to dependencies, specifically for @vercel/build-utils.

@vercel/next@4.20.51 fix

Jul 30, 2026

This patch release addresses an issue with `maxConcurrency` configuration, ensuring that each Next.js route is correctly placed in its own Lambda group, even when sharing the same concurrency limit.

@vercel/nestjs@0.2.111

Jul 30, 2026

@vercel/koa@0.1.90

Jul 30, 2026

@vercel/hono@0.2.110

Jul 30, 2026

@vercel/h3@0.1.116

Jul 30, 2026

@vercel/gatsby-plugin-vercel-builder@2.2.33

Jul 30, 2026

This patch release includes updates to dependencies, specifically for @vercel/build-utils.

@vercel/fs-detectors@6.14.3

Jul 30, 2026

This patch release includes updates to dependencies, specifically for @vercel/build-utils.

@vercel/fastify@0.1.110

Jul 30, 2026

@vercel/express@0.1.121

Jul 30, 2026

This release includes patch updates for @vercel/node and @vercel/cervel. No significant changes or new features are introduced.

@vercel/elysia@0.1.107

Jul 30, 2026

@vercel/connect@0.6.01 feature

Jul 30, 2026

This minor release introduces `connectDiscordCredentials` to the eve integration, enhancing Discord bot token and application ID resolution and interaction verification with Vercel OIDC.

@vercel/client@18.2.31 fix

Jul 30, 2026

This patch release fixes a security vulnerability where `.vercelignore`d files could be re-added during `vercel deploy --prebuilt`. It also updates dependencies.

vercel@58.4.41 fix

Jul 30, 2026

This patch release triggers a new publication to include versions that were missed due to a previous failed release run.

@vercel/cervel@0.1.38

Jul 30, 2026

@vercel/build-utils@13.36.32 fixes

Jul 30, 2026

This patch release includes improvements to how per-function `maxConcurrency` is handled in build outputs, ensuring each Next.js route is in its own Lambda group. It also types shared function settings in container image build outputs.

@vercel/backends@0.8.30

Jul 30, 2026

This patch release includes updates to dependencies, specifically for @vercel/build-utils.

@vercel/static-build@2.11.12

Jul 29, 2026

This is a patch release for @vercel/gatsby-plugin-vercel-builder, version 2.2.32.

@vercel/node@5.9.2

Jul 29, 2026

This patch release includes dependency updates, specifically for @vercel/build-utils.

@vercel/nestjs@0.2.110

Jul 29, 2026

@vercel/koa@0.1.89

Jul 29, 2026

@vercel/hono@0.2.109

Jul 29, 2026

Common Errors

ModuleNotFoundError6 reports

The "ModuleNotFoundError" in Vercel Functions typically arises when the required Python dependencies declared in your `requirements.txt` file haven't been installed before deployment. To fix this, ensure you have a `requirements.txt` file in the root directory of your function's code containing all necessary packages, and verify that Vercel is correctly installing these dependencies during the build process by reviewing the deployment logs for any installation errors.

FetchError2 reports

The "FetchError" in Vercel Functions usually indicates a problem resolving the URL or network connectivity when making an external fetch request. Ensure the URL you are fetching from is publicly accessible and correctly formatted (including `https://`), and that your Vercel function has outbound network access enabled if required (especially when connecting to private resources).