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
Upgrade peerDependencies
of @sentry/nextjs
to next 13
#6046
Comments
curious if this will be a difficult change, since |
To be fair, Turbopack is currently opt-in, so right off the bat there shouldn't be anything breaking in case users explicitly try to use Turbopack. |
I think it would be enough to just check for the |
There is a PR to add it to peer dependencies: #6042, just to unblock people. You're right that full Next 13 support is a bigger question. Opened #6056 to track it. As for turbopack, it's true - if users use it it won't break anything, but the SDK also won't be added to the app at build time, so any code referring to it will just no-op. I've added a note to the docs about that here: getsentry/sentry-docs#5694. |
Problem Statement
Next 13 is out (yay 🥳) – but @sentry/nextjs isn't ready (as of the
peerDependencies
).Solution Brainstorm
Add ^13 to
peerDependencies
(if valid and all goes good of course).The text was updated successfully, but these errors were encountered: