Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node 22 unsupported in vercel serverless adapter #446

Closed
1 task done
Trombach opened this issue Nov 24, 2024 · 0 comments · Fixed by #447
Closed
1 task done

node 22 unsupported in vercel serverless adapter #446

Trombach opened this issue Nov 24, 2024 · 0 comments · Fixed by #447

Comments

@Trombach
Copy link

Astro Info

Astro                    v4.16.14
Node                     v22.10.0
System                   Linux (x64)
Package Manager          pnpm
Output                   hybrid
Adapter                  @astrojs/vercel/serverless
Integrations             @astrojs/tailwind
                         @astrojs/svelte
                         @astrojs/mdx
                         @astrojs/react
                         @astrojs/sitemap
                         @inox-tools/content-utils

Describe the Bug

Vercel has switched to node 22 being the default version: https://vercel.com/docs/functions/runtimes/node-js/node-js-versions. When attempting to deploy Astro with the serverless vercel adapter, the adapter defaults to version 18, because 20 is the latest known version in SUPPORTED_NODE_VERSIONS. This causes the deployment to fail.
Besides 22 being the default now, version 20 is still supported but hasn't been marked as deprecated yet. I would suggest to continue listing version 20 with { status: 'available' } in SUPPORTED_NODE_VERSIONS.

Happy to send a PR!

What's the expected result?

I should be able to deploy Astro to vercel serverless using node version 22.

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-96f9yd?file=package.json

Participation

  • I am willing to submit a pull request for this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant