@sentry/nextjs autoInstrumentServerFunctions should not force all pages to use serverless functions #8323
Labels
Comments
|
Hey @curiousercreative - this seems like a bug on our side, this shouldn't be happening. Could you go through our bug report template and add some details about your SDK version, your next.js version, SDK setup details, details about page vs. app directory, to help us debug. You can just amend the existing issue description instead of creating a new issue. Thank you! |
AbhiPrasad
added
Status: Needs Information
Package: nextjs
hubertdeng123
added
Waiting for: Community
and removed
Status: Needs Information
labels
getsantry
bot
moved this from Waiting for: Product Owner
to Waiting for: Community
in GitHub Issues with 👀
|
Closing this issue for cleanup. Please re-open if this still applies. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
With a default configuration for nextjs and deployed to Vercel.com, every route/page is forced to use serverless functions even when they would otherwise be SSG. I only noticed this fact today when an AWS outage in our particular region took down our entire production deployment, not a single page would load and instead would respond with an internal server error.
Solution Brainstorm
The default behavior for
autoInstrumentServerFunctions: trueshould not force Next.js static pages to become server-side rendered.The text was updated successfully, but these errors were encountered: