Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
kakadiadarpan
approved these changes
Feb 16, 2026
Merged
kakadiadarpan
pushed a commit
that referenced
this pull request
Feb 16, 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 the packages will be published to npm automatically. 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/[email protected] ### Patch Changes - [#190](#190) [`41d4511`](41d4511) Thanks [@mischnic](https://github.com/mischnic)! - fix: don't inline system env vars Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
My understanding is that all of this code runs only server-side
In that case, there is no benefit to trying to fallback to
NEXT_PUBLIC_VERCEL_URL(the only case where it's necessary is for client-side code, where there is obviously noprocess.envat runtime.)This means that the JS chunks in the serverless function are now deterministic as
NEXT_PUBLIC_always inlined the value into the JS chunk