fix: update getNodeVersion to getRuntimeNodeVersion #595
Conversation
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
The function getNodeVersion was renamed to getRuntimeNodeVersion in @vercel/build-utils package (vercel/vercel#14600). This change fixes the deployment error: Error: (0 , build_utils_1.getNodeVersion) is not a function Fixes vercel-community#594
|
Looks good. getNodeVersion() is also failing my deployment. |
+1, hopefully this gets merged on priority. |
f3l1x
approved these changes
Jan 15, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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
In
@vercel/build-utils, the functiongetNodeVersionhas been renamed togetRuntimeNodeVersion(vercel/vercel#14600), which causes the build to fail.This PR updates the import and function call to use the new function name.
Fixes #594
Error
Error: (0 , build_utils_1.getNodeVersion) is not a function
Changes
getNodeVersion→getRuntimeNodeVersion(line 10)getNodeVersion(workPath)→getRuntimeNodeVersion(workPath)(line 117)Related