-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
@sentry/next.js 7.31 breaks Storybook build #6808
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
Labels
Package: nextjs
Issues related to the Sentry Nextjs SDK
Comments
Hi, thanks for this awesome error report! Pointing us toward the browser field helped a ton. A fix will soon be released (probably within a day). |
Awesome, thanks so much for the fast response! |
Also,
|
3 tasks
Can confirm that this is fixed in v7.31.1. |
@connor-baer Thanks for confirming! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which package are you using?
@sentry/nextjs
SDK Version
7.31.0
Framework Version
[email protected]
Link to Sentry event
No response
SDK Setup
Steps to Reproduce
My project uses Next.js v12.2.5, Sentry v7.31, and Storybook v6.4.20. After upgrading to
@sentry/nextjs
v7.31, Storybook fails to build (see error below). The Next.js app builds fine.Some components that are rendered in Storybook import Sentry. I've traced the issue to the removal of the
browser
field in thepackage.json
file in #6753 which causes Storybook to attempt to import Node-specific code to the client bundle. Re-adding the field seems to fix the issue.Expected Result
Storybook builds without error
Actual Result
The text was updated successfully, but these errors were encountered: