You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, next dev has a node version check that is using the users defined node version. This does not work correctly when using a runtime from a binary (For example running bun binary). For example if user has node16 but is using bun which is compatible up to node23. This still fails. I wonder if there's a config or env variable I can set to bypass this check.
Setting the env variable __NEXT_REQUIRED_NODE_VERSION_RANGE or NODE_VERSION does not work. Thanks!
Additional information
if(!semver.satisfies(process.versions.node,process.env.__NEXT_REQUIRED_NODE_VERSION_RANGE!,{includePrerelease: true})){console.error(`You are using Node.js ${process.versions.node}. For Next.js, Node.js version "${process.env.__NEXT_REQUIRED_NODE_VERSION_RANGE}" is required.`)process.exit(1)}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
Currently, next dev has a node version check that is using the users defined node version. This does not work correctly when using a runtime from a binary (For example running bun binary). For example if user has node16 but is using bun which is compatible up to node23. This still fails. I wonder if there's a config or env variable I can set to bypass this check.
Setting the env variable
__NEXT_REQUIRED_NODE_VERSION_RANGE
orNODE_VERSION
does not work. Thanks!Additional information
https://github.com/vercel/next.js/blob/main/packages/next/src/bin/next.ts#L24
Example
While system node version is 16
Beta Was this translation helpful? Give feedback.
All reactions