-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Next.js Edge Runtime fetch
tracing
#6804
Comments
@lforst - I'm curious about the scope of this issue. Does it cover Edge API routes not sending Sentry issues entirely? Your note about it working for local builds made me want to verify. Or is this a separate issue? Example Repro Steps (repo link)
Side note: The error does show up in Sentry when navigating to that url in a browser but I'm assuming that's because it's a client side error |
@zcarlson-gmgt this issue is not related to what you think it is. This is about instrumenting As for your example: Edge error reporting currently doesn't work in dev mode. I could verify with your example that it does indeed work for prod builds. |
@lforst oh wow thank you! Glad it was simple! |
Problem Statement
The Next.js SDK currently doesn't trace
fetch
calls on the edge runtime:Solution Brainstorm
A quick test showed that using our browser implementation to patch
fetch
works for local builds but doesn't on Vercel.Potential solutions:
fetch
through collaboration with VercelThe text was updated successfully, but these errors were encountered: