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

Cannot build "astro template blog" on Vercel (Node.js Version 22.x) #471

Closed
1 task
cworld1 opened this issue Dec 6, 2024 · 1 comment · Fixed by #472
Closed
1 task

Cannot build "astro template blog" on Vercel (Node.js Version 22.x) #471

cworld1 opened this issue Dec 6, 2024 · 1 comment · Fixed by #472
Labels
needs triage Issue needs to be triaged

Comments

@cworld1
Copy link

cworld1 commented Dec 6, 2024

Astro Info

pnpm astro info

> astro-blog-test@0.0.1 astro D:\code\test\astro-blog-test
> astro "info"

Astro                    v5.0.3
Node                     v23.3.0
System                   Windows (x64)
Package Manager          pnpm
Output                   server
Adapter                  @astrojs/vercel
Integrations             @astrojs/mdx
                         @astrojs/sitemap

If this issue only occurs in one browser, which browser is a problem?

Firefox

Describe the Bug

Create using:

pnpm create astro@latest -- --template blog
cd ./astro-blog-test/
pnpm i @astrojs/vercel
nvim ./astro.config.mjs
# Then upload to github and deploy to vercel

Vercel output:

[16:09:56.732] Running build in Washington, D.C., USA (East) – iad1
[16:09:56.841] Cloning github.com/cworld1/astro-blog-test (Branch: main, Commit: e6c2a7c)
[16:09:57.117] Cloning completed: 276.04ms
[16:09:57.196] Previous build cache not available
[16:09:57.466] Running "vercel build"
[16:09:57.889] Vercel CLI 39.1.3
[16:09:58.601] Detected `pnpm-lock.yaml` version 9 generated by pnpm@9.x
[16:09:58.612] Installing dependencies...
[16:09:59.397] Lockfile is up to date, resolution step is skipped
[16:09:59.461] Progress: resolved 1, reused 0, downloaded 0, added 0
[16:09:59.533] Packages: +391
[16:09:59.534] ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
[16:10:00.464] Progress: resolved 391, reused 0, downloaded 54, added 40
[16:10:01.467] Progress: resolved 391, reused 0, downloaded 179, added 170
[16:10:02.468] Progress: resolved 391, reused 0, downloaded 276, added 267
[16:10:03.468] Progress: resolved 391, reused 0, downloaded 340, added 330
[16:10:03.703] Progress: resolved 391, reused 0, downloaded 391, added 391, done
[16:10:03.875] .../esbuild@0.21.5/node_modules/esbuild postinstall$ node install.js
[16:10:03.876] .../esbuild@0.24.0/node_modules/esbuild postinstall$ node install.js
[16:10:03.876] .../sharp@0.33.5/node_modules/sharp install$ node install/check
[16:10:04.588] .../esbuild@0.21.5/node_modules/esbuild postinstall: Done
[16:10:04.617] .../esbuild@0.24.0/node_modules/esbuild postinstall: Done
[16:10:04.801] .../sharp@0.33.5/node_modules/sharp install: Done
[16:10:04.879] 
[16:10:04.880] dependencies:
[16:10:04.880] + @astrojs/mdx 4.0.1
[16:10:04.880] + @astrojs/rss 4.0.10
[16:10:04.880] + @astrojs/sitemap 3.2.1
[16:10:04.880] + @astrojs/vercel 8.0.0
[16:10:04.880] + astro 5.0.3
[16:10:04.881] 
[16:10:04.884] Done in 6.1s
[16:10:04.914] Running "pnpm run build"
[16:10:05.424] 
[16:10:05.424] > astro-blog-test@0.0.1 build /vercel/path0
[16:10:05.424] > astro build
[16:10:05.424] 
[16:10:07.726] 08:10:07 [content] Syncing content
[16:10:07.727] 08:10:07 [content] Content config changed
[16:10:07.727] 08:10:07 [content] Astro version changed
[16:10:07.727] 08:10:07 [content] Clearing content store
[16:10:08.226] 08:10:08 [content] Synced content
[16:10:08.227] 08:10:08 [types] Generated 1.17s
[16:10:08.228] 08:10:08 [build] output: "server"
[16:10:08.228] 08:10:08 [build] directory: /vercel/path0/dist/
[16:10:08.228] 08:10:08 [build] adapter: @astrojs/vercel
[16:10:08.229] 08:10:08 [build] Collecting build info...
[16:10:08.229] 08:10:08 [build] ✓ Completed in 1.20s.
[16:10:08.233] 08:10:08 [build] Building server entrypoints...
[16:10:09.549] 08:10:09 [WARN] [router] getStaticPaths() ignored in dynamic page /src/pages/blog/[...slug].astro. Add `export const prerender = true;` to prerender the page as static HTML during the build process.
[16:10:11.103] 08:10:11 [vite] �[32m✓ built in 2.83s�[39m
[16:10:11.104] 08:10:11 [build] ✓ Completed in 2.87s.
[16:10:11.125] 
[16:10:11.126]  prerendering static routes 
[16:10:11.126] 08:10:11 ✓ Completed in 10ms.
[16:10:11.126] 
[16:10:11.127] 08:10:11 [build] Rearranging server assets...
[16:10:11.141] 08:10:11 [WARN] [@astrojs/vercel] 
[16:10:11.142] 	The local Node.js version (22) is not supported by Vercel Serverless Functions.
[16:10:11.142] 	Your project will use Node.js 18 as the runtime instead.
[16:10:11.142] 	Consider switching your local version to 18.
[16:10:11.142] 
[16:10:11.142] 08:10:11 [@astrojs/vercel] Bundling function ../../../../dist/server/entry.mjs
[16:10:12.234] 08:10:12 [@astrojs/sitemap] `sitemap-index.xml` created at `dist/client`
[16:10:12.234] 08:10:12 [build] Server built in 5.21s
[16:10:12.234] 08:10:12 [build] Complete!
[16:10:12.313] Build Completed in /vercel/output [14s]
[16:10:12.363] Deploying outputs...
[16:10:12.371] Error: The following Serverless Functions contain an invalid "runtime":
[16:10:12.371]   - _render (nodejs18.x). Learn More: https://vercel.com/guides/serverless-function-contains-invalid-runtime-error
[16:10:12.527] 

What's the expected result?

Build correctly on vercel.

Link to Minimal Reproducible Example

https://github.com/cworld1/astro-blog-test

Participation

  • I am willing to submit a pull request for this issue.
@github-actions github-actions bot added the needs triage Issue needs to be triaged label Dec 6, 2024
@cworld1 cworld1 changed the title Cannot build "astro template blog" on vercel Cannot build "astro template blog" on Vercel (Node.js Version 22.x) Dec 6, 2024
@bluwy bluwy transferred this issue from withastro/astro Dec 6, 2024
@bluwy
Copy link
Member

bluwy commented Dec 6, 2024

It was fixed in #447 but looks like the change got lost in the latest major

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage Issue needs to be triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants