-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Webpack ChunkLoadErrors Filtered out #57458
Comments
Assigning to @getsentry/support for routing ⏲️ |
Routing to @getsentry/product-owners-issues for triage ⏲️ |
Besides what @smeubank proposed - We could try to group all these errors together - explain to users that they should capture the error in their app and refresh the page. But since it's a valid error, this approach might maintain trust in Sentry and our reporting. |
It could be a new Issue Type - where instead of us showing a Stacktrace, we explain what the error is: "This error happens when your the users bundle isn't refreshed when you do a new deploy. To fix this capture this error in your application and prompt the user to refresh the page." |
We also need a grouping rule to ensure that all ChunkLoadErrors get grouped together. We want to add more help text to help people debug the error and link to the filter to turn it on if they don't want to see those types of errors. |
Action items:
|
Problem Statement
ChunkLoadErrors are not new, but seem to be impacting NextJS devs working with AppDir disproportionately. This leads to a buggy page or just a white page, it seems.
The problem is these errors are not very actionable all the time, and can happen often which simply leads to consuming a lot of Sentry quota.
As a fix there is now an inbound filter on by default, good for quota, bad for visibilty. Is there way we can ensure users are still alerted to this problem, without killing their quota?
As seen in examples like this, Sentry plays an important role in telling developers that this problem exists
Solution Brainstorm
Background
Was surfaced on twitter with link to error on NextjS
vercel/next.js#38507
The text was updated successfully, but these errors were encountered: