Is the CLI expected to disallow Node 22?

Help
1

Because of my dependency to pdfjs-dist I’ve set Node 22 as a minimum version for my Next.js application. Using GitHub workflows and the available actions, my CI fails when reaching the Vercel steps because of the Node version requirement.

Vercel CLI 37.3.0
Error: Found invalid Node.js Version: ">=22.7.0". Please set "engines": { "node": "20.x" } in your `package.json` file to use Node.js 20.

I confirmed that the Node version that is pulled fulfills the query from package.json. I see no mention of Node 22 being unsupported specifically. Is this expected behavior?

2

Hi @angrybacon! The build image currently has support for Node.js versions 20, 18, and 16. Node.js 22 will enter long-term support (LTS) in October and should be available for new builds around the same time.

1 Like
3

Duly noted, thanks for letting me know

1 Like
4

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.