-
-
Notifications
You must be signed in to change notification settings - Fork 49
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
@astrojs/vercel
- AdapterSupportOutputMismatch
#430
Comments
Looks like we need to update the vercel adapter code here to use the value of adapters/packages/vercel/src/index.ts Lines 277 to 289 in aed689d
setAdapter uses the right value that doesn't trigger the error.
That solves this issue, however it also looks like vercel is using the adapters/packages/vercel/src/index.ts Lines 196 to 207 in aed689d
Unless there's a way to share the same config in agnostic of server or static, @ematipico I think making |
Is there a case where |
It should only ever go from I've discussed with Erika before if we could detect the case where the user set |
I'm also experiencing this problem |
Having the same issue here. Output set to static as almost the entire site is static bar a couple of /api routes but using the @astro/vercel adaptor I am seeing In the single api route I currently have I have Using the @astro/node adapter it all works as expected locally and respects the idea that all pages are static unless the 'opt out' of prerendering has been set. |
Astro Info
If this issue only occurs in one browser, which browser is a problem?
No response
Describe the Bug
After upgrading to
"astro": "5.0.0-beta.6"
and"@astrojs/vercel": "8.0.0-beta.3"
I get an error:From what I understand,
static
is a correct output if just a few pages/endpoints haveexport const prerender = false;
In the linked reproduction, run
npm run build
to repro the error.What's the expected result?
Successful build.
Link to Minimal Reproducible Example
https://stackblitz.com/edit/withastro-astro-fewhsc?file=package.json
Participation
The text was updated successfully, but these errors were encountered: