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

Throw warning if someone uses NextJS experimental-edge-runtime #5974

Closed
AbhiPrasad opened this issue Oct 17, 2022 · 1 comment · Fixed by #6683
Closed

Throw warning if someone uses NextJS experimental-edge-runtime #5974

AbhiPrasad opened this issue Oct 17, 2022 · 1 comment · Fixed by #6683
Assignees
Labels
Package: nextjs Issues related to the Sentry Nextjs SDK Type: Improvement

Comments

@AbhiPrasad
Copy link
Member

Problem Statement

The SDK does not support NextJS experimental-edge-runtime as per #4206.

Solution Brainstorm

User hit issues all the time where they try to use experimental-edge-runtime and things break. Until we have proper support for it, we should emit a warning during build time against this.

@wconnorwalsh
Copy link

It isn't just the experimental-edge-runtime that is the issue – it's also the generally available middleware (first introduced nearly a year ago).

Emitting a warning at build time is not good enough. This is a major part of the future of NextJS/Vercel platform and it is only a short amount of time before all of it is out of beta. Until Sentry can support this, new features in minor releases that are silently failing in the edge-runtime (e.g., autoInstrumentServerFunctions) should be disabled by default.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Package: nextjs Issues related to the Sentry Nextjs SDK Type: Improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants