Skip to content

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

Description

@s1gr1d

#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 feat(vue,nuxt): Record default UI spans without Options API (mixins) #24174 (parity only), it lives in that PR's history. This would make async root spans in Nuxt applications with <Suspense> appear longer.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions