Guard missing Vercel Flags runtime helpers#326
Merged
dferber90 merged 5 commits intovercel:mainfrom Mar 12, 2026
Merged
Conversation
Contributor
|
@zzvxdoteth is attempting to deploy a commit to the Vercel Team on Vercel. A member of the Team first needs to authorize it. |
zzvxdoteth
changed the title
dferber90
approved these changes
Mar 12, 2026
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
|
Thank you for resolving this! Released as
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Guards internal Vercel Flags runtime helpers when Vercel does not expose the expected callable functions during evaluation.
Closes #325.
What changed
reportValue/internalReportValuebefore calling the request-context hook@vercel/flags-definitionsresolves without a callablegetexportflagsand@vercel/flags-coreWhy
Both of these hooks are optional runtime plumbing from Vercel's environment. If either one is malformed or omitted, flag evaluation should degrade gracefully instead of throwing a
TypeError.Verification
pnpm -C packages/flags checkpnpm -C packages/flags type-checkpnpm -C packages/flags testpnpm -C packages/vercel-flags-core checkpnpm -C packages/vercel-flags-core type-checkpnpm -C packages/vercel-flags-core test