-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
feat: enable sentry features #6133
feat: enable sentry features #6133
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Lighthouse Results
|
7c2e3dc
to
89b0e51
Compare
@AbhiPrasad I've noticed by using the Sentry Client the way we are (with BrowserClient) the client-side requests are not going through Is there something else we need to configure? |
I was able to make a fix, by 👀 Sentry's source code. |
cc @nodejs/web-infra for reviewes :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some small comments within.
it all tracks with what we discussed on the call - but i'll admit I won't be surprised if we need to tweak things further post-deployment
Description
This PR attempts to tree-shake irrelevant Sentry parts and load a minimal Sentry Browser Client for our Next.js installation.
This PR should also disable support of UnhandledPromise rejection from Sentry
Notice that two unrelated changes in this PR are two tiny hot fixes (1 removing a console).timeEnd, 2 fixing a bug that if no static data is generated HomeDownloadButton crashes due to node release data being empty)
Validation
I've seen no bundle increase with this setup, which is intriguing. The expected outcome here is for all Sentry features to be working correctly.
cc @AbhiPrasad @JonasBa for review from Sentry side
cc @bmuenzenmeyer for internal review