Skip to content

log functions exceeding the 250MB size limit#14067

Merged
vikhyathdevadiga merged 14 commits intomainfrom
vikhyath/log-functions-exceeding-250mb
Feb 13, 2026
Merged

log functions exceeding the 250MB size limit#14067
vikhyathdevadiga merged 14 commits intomainfrom
vikhyath/log-functions-exceeding-250mb

Conversation

@vikhyathdevadiga
Copy link
Copy Markdown
Contributor

@vikhyathdevadiga vikhyathdevadiga commented Oct 8, 2025

Adds opt-in serverless function size analysis (requires an environment variable VERCEL_ANALYZE_BUILD_OUTPUT=1) to detect and report functions exceeding the 250MB uncompressed size limit. The output will contain:

  • Functions that exceed the size limit with their total uncompressed size
  • A breakdown of the top 10 largest dependencies
  • A summary of normal functions under the limit

Note

Low Risk Change

This PR adds opt-in build output analysis functionality gated by an environment variable to detect and report serverless functions exceeding size limits, with no security, auth, or data integrity changes.

  • Adds new analysis functions to detect functions exceeding 250MB size limit
  • Feature gated behind VERCEL_ANALYZE_BUILD_OUTPUT=1 environment variable
  • Throws NowBuildError when functions exceed size limit

Risk assessment for commit facf1d5.

@changeset-bot
Copy link
Copy Markdown

changeset-bot bot commented Oct 8, 2025

🦋 Changeset detected

Latest commit: facf1d5

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
vercel Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Oct 8, 2025

🧪 Unit Test Strategy

Comparing: ef1be64facf1d5 (view diff)

Strategy: Affected packages only

✅ Only testing packages that have been modified or depend on modified packages.

Affected packages - 1 (3%)
  1. vercel
Unaffected packages - 39 (98%)
  1. @vercel-internals/get-package-json
  2. @vercel/backends
  3. @vercel/build-utils
  4. @vercel/cervel
  5. @vercel/cli-auth
  6. @vercel/client
  7. @vercel/config
  8. @vercel/detect-agent
  9. @vercel/edge
  10. @vercel/elysia
  11. @vercel/error-utils
  12. @vercel/express
  13. @vercel/fastify
  14. @vercel/firewall
  15. @vercel/frameworks
  16. @vercel/fs-detectors
  17. @vercel/functions
  18. @vercel/gatsby-plugin-vercel-builder
  19. @vercel/go
  20. @vercel/h3
  21. @vercel/hono
  22. @vercel/hydrogen
  23. @vercel/koa
  24. @vercel/nestjs
  25. @vercel/next
  26. @vercel/node
  27. @vercel/oidc
  28. @vercel/oidc-aws-credentials-provider
  29. @vercel/python
  30. @vercel/python-analysis
  31. @vercel/redwood
  32. @vercel/related-projects
  33. @vercel/remix-builder
  34. @vercel/routing-utils
  35. @vercel/ruby
  36. @vercel/rust
  37. @vercel/static-build
  38. @vercel/static-config
  39. examples

Results

  • Unit tests: Only affected packages will run unit tests
  • E2E tests: Handled separately (Version Packages PRs or run-e2e-tests label)
  • Type checks: Only affected packages will run type checks

This comment is automatically generated based on the affected testing strategy

…s-exceeding-250mb

# Conflicts:
#	packages/cli/src/commands/build/index.ts
analyzeSingleFunction only measured FileFsRef entries from filePathMap,
missing FileBlob files, zipBuffer contents, and .vc-config.json itself.
Now walks the .func directory to capture those, then adds filePathMap
entries (which live outside .func).
@github-actions
Copy link
Copy Markdown
Contributor

📦 CLI Tarball Ready

The Vercel CLI tarball for this PR is now available!

Quick Test

You can test this PR's CLI directly by running:

npx https://vercel-5op0lgojf.vercel.sh/tarballs/vercel.tgz --help

Use in vercel.json

To use this CLI version in your project builds, add to your vercel.json:

{
  "build": {
    "env": {
      "VERCEL_CLI_VERSION": "vercel@https://vercel-5op0lgojf.vercel.sh/tarballs/vercel.tgz"
    }
  }
}

@vikhyathdevadiga vikhyathdevadiga merged commit f278d46 into main Feb 13, 2026
135 checks passed
@vikhyathdevadiga vikhyathdevadiga deleted the vikhyath/log-functions-exceeding-250mb branch February 13, 2026 03:31
mehulkar pushed a commit that referenced this pull request Feb 13, 2026
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and publish to npm
yourself or [setup this action to publish
automatically](https://github.com/changesets/action#with-publishing). If
you're not ready to do a release yet, that's fine, whenever you add more
changesets to main, this PR will be updated.


# Releases
## vercel@50.17.0

### Minor Changes

- Install builder packages on demand
([#15023](#15023))

- Display functions exceeding 250MB uncompressed size limit with total
size and breakdown of largest dependencies (requires environment
variable VERCEL_ANALYZE_BUILD_OUTPUT=1).
([#14067](#14067))

### Patch Changes

- Add `--format=json` option to `vercel integration list` and show
project name in table header when results are scoped to a project
([#15007](#15007))

- Fix builder import resolution from pre-installed depenencies
([#15041](#15041))

- Services routing improvements:
([#15018](#15018))

- Fix route ownership scoping so parent service catch-alls (e.g. Vite
SPA fallback) don't capture sibling service prefixes
- Move shared ownership-guard helpers (`getOwnershipGuard`,
`scopeRouteSourceToOwnership`) to `@vercel/routing-utils`
- Place runtime service function outputs under internal
`/_svc/<service>/index` namespace to prevent filesystem path leakage
    -   Block `/_svc` as a reserved routePrefix in service validation
- Scope all builder-emitted routes (not just route-owning builders) to
their service ownership before merging

-   Updated dependencies \[]:
    -   @vercel/static-build@2.8.37
    -   @vercel/build-utils@13.4.0
    -   @vercel/next@4.15.28
    -   @vercel/redwood@2.4.9
    -   @vercel/rust@1.0.5

## @vercel/client@17.2.41

### Patch Changes

- Updated dependencies
\[[`3cd0b559f1815fdb13f7aa05114bae2b0b0b0e68`](3cd0b55)]:
    -   @vercel/routing-utils@5.3.3
    -   @vercel/build-utils@13.4.0

## @vercel/fs-detectors@5.8.6

### Patch Changes

- Services routing improvements:
([#15018](#15018))

- Fix route ownership scoping so parent service catch-alls (e.g. Vite
SPA fallback) don't capture sibling service prefixes
- Move shared ownership-guard helpers (`getOwnershipGuard`,
`scopeRouteSourceToOwnership`) to `@vercel/routing-utils`
- Place runtime service function outputs under internal
`/_svc/<service>/index` namespace to prevent filesystem path leakage
    -   Block `/_svc` as a reserved routePrefix in service validation
- Scope all builder-emitted routes (not just route-owning builders) to
their service ownership before merging

- Updated dependencies
\[[`3cd0b559f1815fdb13f7aa05114bae2b0b0b0e68`](3cd0b55)]:
    -   @vercel/routing-utils@5.3.3
    -   @vercel/frameworks@3.17.1

## @vercel/routing-utils@5.3.3

### Patch Changes

- Services routing improvements:
([#15018](#15018))

- Fix route ownership scoping so parent service catch-alls (e.g. Vite
SPA fallback) don't capture sibling service prefixes
- Move shared ownership-guard helpers (`getOwnershipGuard`,
`scopeRouteSourceToOwnership`) to `@vercel/routing-utils`
- Place runtime service function outputs under internal
`/_svc/<service>/index` namespace to prevent filesystem path leakage
    -   Block `/_svc` as a reserved routePrefix in service validation
- Scope all builder-emitted routes (not just route-owning builders) to
their service ownership before merging


<!-- VADE_RISK_START -->
> [!NOTE]
> Low Risk Change
>
> This PR is an automated Changesets release that only updates version
numbers in package.json files and adds changelog entries - no source
code changes are present.
> 
> - Deletes changeset markdown files after consuming them
> - Bumps version numbers in 4 package.json files
> - Adds changelog entries documenting previous changes
>
> <sup>Risk assessment for [commit
9186d29](https://github.com/vercel/vercel/commit/9186d293adee9d555b8582f5c1d0cec87689acf1).</sup>
<!-- VADE_RISK_END -->

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants