-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Open
Open
Copy link
Labels
feat: browserIssues and PRs related to the browser runnerIssues and PRs related to the browser runnerfeat: open telemetryp2-nice-to-haveNot breaking anything but nice to have (priority)Not breaking anything but nice to have (priority)
Description
Clear and concise description of the problem
Context
In browser mode, Vitest cannot automatically propagate openTelemetry async context due to lack of async_hooks. User-defined spans often lose parent context across async operations (promises, timers, events), leading to incomplete or flat tracing. Internal spans are manually linked, but user/test code loses context in deeply async code paths.
Suggested solution
Explore robust async context tracking for browsers (e.g. zone.js or context polyfills), expose helpers in Vitest to allow manual context handling for user code, and document current limitations and any recommended workarounds for reliable tracing.
Alternative
No response
Additional context
No response
Validations
- Follow our Code of Conduct
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
Metadata
Metadata
Assignees
Labels
feat: browserIssues and PRs related to the browser runnerIssues and PRs related to the browser runnerfeat: open telemetryp2-nice-to-haveNot breaking anything but nice to have (priority)Not breaking anything but nice to have (priority)