Follow-ups: Vue UI spans after #24174 (component tracking)

Open

#24,460 opened on Sep 17, 2026 1 comment 0 reactions 1 assignee View on GitHub

@s1gr1d is already working on this.

Since Sep 17, 2026.

Assessment

This issue has not been assessed yet.

Spans Vue

https://github.com/getsentry/sentry-javascript/pull/24174 records the default spans (Application Render, Vue <Root>) without app.mixin(). Component tracking still needs the Options API, and a few loose ends remain.

Docs The Vue and Nuxt component tracking pages should match the SDK. Currently, they miss the Options API requirement (vue: { optionsApi: true } on Nuxt 5) and state wrong facts: default hooks are ['activate', 'mount'] not ['activate', 'mount', 'update'], the op is ui.render not ui.vue.render, the timeout never "waits for the last component" (debounce timers are per component), and the root is always tracked.
Application Render coverage The span ends at the root's initial mount on every path. Late children never extended it because the mixin arms one debounce timer per component instead of on the root. A <Suspense>-based extension for Nuxt was built and removed from #24174 (parity only), it lives in that PR's history. This would make async root spans in Nuxt applications with <Suspense> appear longer.

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.