Repository navigation
Improve Next.js Issues #85531
Description
Issues can be very noisy, due to poor grouping, low quality stack traces, browser extension errors, and more. This issue is a collection of Issues and sub-epics to improve the issues experience for Next.js, by connection all other React and browser frameworks.
P0
- feat(nextjs): Do not strip origin information from different origin stack frames sentry-javascript#15418
- [JavaScript] Next.js #78904 (comment)
- [source maps debugger] Feedback Link is broke #85730
- Sourcemaps Wizard NextJS flow doesn't jump directly to sourcemaps configuration sentry-wizard#812
P1
- Unparametrized Paths Not as Useful sentry-javascript#15411
- Next.js Turbopack Support sentry-javascript#8105
P2
P3
- Remove Sentry SDK info from stack trace #85233
- Discern Client vs Server Errors #85732
- is there an issue with stack locals?
Metadata
Metadata
Assignees
Projects
- Status
Activity
smeubank commentedon Feb 20, 2025
consider issues flagged as 3rd party JavaScript in Sentry and Codecov dashboards for potential other issues we should be dropping for users.
I'm curious if these changes with rewrite frames changes, will enrich these and/or duplicate them. It also means the 3 projects referenced in those 2 dashboard are interesting test candidates for experimental changes before we release this to larger audience of Sentry users.
cc @chargome
getsantry commentedon Feb 20, 2025
Routing to @getsentry/product-owners-issues for triage ⏲️
getsantry commentedon Feb 20, 2025
Routing to @getsentry/product-owners-issues-source-maps for triage ⏲️
feat(core): Default filter unactionable error (#15527)
mydea commentedon Jul 1, 2025
I will close this in favor of other, new issues we have where we are tracking this more detailed already.