-
-
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
withSentryConfig breaks unstable_allowDynamic #8386
Labels
Comments
Thanks for raising this! I just tested this with the latest state of our develop branch and the error you shared didn't occur. We did some changes between the latest release and now so maybe this is already fixed. |
That's great news. Any idea when that will ship? |
@grantmagdanz Likely next week! |
I can confirm this is fixed in 7.64.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
7.56.0
Framework Version
next 13.4.6
Link to Sentry event
No response
SDK Setup
You can find a simple repo with the setup here: https://github.com/grantmagdanz/sentry-unstable_allowDynamic-repro
Steps to Reproduce
yarn build
and see the errorskipSentry = true
innext.config.js
yarn build
again and see the build success correctlyI instrumented the next code and it looks like withSentryConfig is doing something that messes up the routes. At this check,
route
is null sounstable_allowDynamic
doesn't existExpected Result
Build succeeds. More info on unstable_allowDynamic here.
Actual Result
Build fails:
The text was updated successfully, but these errors were encountered: