Triage Report

Issue Triage: #<number>

Title: <title> Classification: <bug|feature request|documentation|support|duplicate> Affected Package(s): @sentry/<package>, ... Priority: <high|medium|low> Complexity: <trivial|moderate|complex>

Summary

<1-2 sentence summary of the issue>

Root Cause Analysis

<Detailed explanation with file:line code pointers when SDK-side; or clear statement that cause is setup/environment/usage and what correct setup would look like. Reference specific functions, variables, and logic paths where applicable.>

Alternative interpretations / Recommended approach

<Include ONLY when the reporter’s framing or proposed fix is not ideal. One or two sentences: preferred interpretation (e.g. incorrect SDK setup vs bug, docs link vs new content) and the recommended action. Otherwise, omit this section.>

Information gaps / Uncertainty

<Include ONLY when key information could not be gathered. Bullet list: what is missing (e.g. reproduction steps, stack trace, affected package) and what would be needed to proceed. Otherwise, omit this section.>

Related Issues & PRs

• #<number> - <title> (<open|closed|merged>)
• (or "No related issues found")

Cross-Repo Findings

• bundler-plugins: <findings or "no matches">
• sentry-docs: <findings or "no matches">

Recommended Next Steps

1. <specific action item>
2. <specific action item>
3. ...