Composition API: Lifecycle Hooks

Usage Note

All APIs listed on this page must be called synchronously during the setup() phase of a component. See Guide - Lifecycle Hooks for more details.

onMounted()

Registers a callback to be called after the component has been mounted.

Type

function onMounted(callback: () => void): void

Details
A component is considered mounted after:
- All of its synchronous child components have been mounted (does not include async components or components inside <Suspense> trees).
- Its own DOM tree has been created and inserted into the parent container. Note it only guarantees that the component's DOM tree is in-document if the application's root container is also in-document.
This hook is typically used for performing side effects that need access to the component's rendered DOM, or for limiting DOM-related code to the client in a server-rendered application.
This hook is not called during server-side rendering.

Example

Accessing an element via template ref:

vue

<script setup>
import { ref, onMounted } from 'vue'

const el = ref()

onMounted(() => {
  el.value // <div>
})
</script>

<template>
  <div ref="el"></div>
</template>

onUpdated()

Registers a callback to be called after the component has updated its DOM tree due to a reactive state change.

Type

function onUpdated(callback: () => void): void

Details
A parent component's updated hook is called after that of its child components.
This hook is called after any DOM update of the component, which can be caused by different state changes. If you need to access the updated DOM after a specific state change, use nextTick() instead.
This hook is not called during server-side rendering.
WARNING
Do not mutate component state in the updated hook - this will likely lead to an infinite update loop!

Example

Accessing updated DOM:

vue

<script setup>
import { ref, onUpdated } from 'vue'

const count = ref(0)

onUpdated(() => {
  // text content should be the same as current `count.value`
  console.log(document.getElementById('count').textContent)
})
</script>

<template>
  <button id="count" @click="count++">{{ count }}</button>
</template>

onUnmounted()

Registers a callback to be called after the component has been unmounted.

Type

function onUnmounted(callback: () => void): void

Details
A component is considered unmounted after:
- All of its child components have been unmounted.
- All of its associated reactive effects (render effect and computed / watchers created during setup()) have been stopped.
Use this hook to clean up manually created side effects such as timers, DOM event listeners or server connections.
This hook is not called during server-side rendering.

Example

vue

<script setup>
import { onMounted, onUnmounted } from 'vue'

let intervalId
onMounted(() => {
  intervalId = setInterval(() => {
    // ...
  })
})

onUnmounted(() => clearInterval(intervalId))
</script>

onBeforeMount()

Registers a hook to be called right before the component is to be mounted.

Type

function onBeforeMount(callback: () => void): void

Details
When this hook is called, the component has finished setting up its reactive state, but no DOM nodes have been created yet. It is about to execute its DOM render effect for the first time.
This hook is not called during server-side rendering.

onBeforeUpdate()

Registers a hook to be called right before the component is about to update its DOM tree due to a reactive state change.

Type

function onBeforeUpdate(callback: () => void): void

Details
This hook can be used to access the DOM state before Vue updates the DOM. It is also safe to modify component state inside this hook.
This hook is not called during server-side rendering.

onBeforeUnmount()

Registers a hook to be called right before a component instance is to be unmounted.

Type

function onBeforeUnmount(callback: () => void): void

Details
When this hook is called, the component instance is still fully functional.
This hook is not called during server-side rendering.

onErrorCaptured()

Registers a hook to be called when an error propagating from a descendant component has been captured.

Type

function onErrorCaptured(callback: ErrorCapturedHook): void

type ErrorCapturedHook = (
  err: unknown,
  instance: ComponentPublicInstance | null,
  info: string
) => boolean | void

Details
Errors can be captured from the following sources:
- Component renders
- Event handlers
- Lifecycle hooks
- setup() function
- Watchers
- Custom directive hooks
- Transition hooks
The hook receives three arguments: the error, the component instance that triggered the error, and an information string specifying the error source type.
You can modify component state in errorCaptured() to display an error state to the user. However, it is important that the error state should not render the original content that caused the error; otherwise the component will be thrown into an infinite render loop.
The hook can return false to stop the error from propagating further. See error propagation details below.
Error Propagation Rules
- By default, all errors are still sent to the application-level app.config.errorHandler if it is defined, so that these errors can still be reported to an analytics service in a single place.
- If multiple errorCaptured hooks exist on a component's inheritance chain or parent chain, all of them will be invoked on the same error, in the order of bottom to top. This is similar to the bubbling mechanism of native DOM events.
- If the errorCaptured hook itself throws an error, both this error and the original captured error are sent to app.config.errorHandler.
- An errorCaptured hook can return false to prevent the error from propagating further. This is essentially saying "this error has been handled and should be ignored." It will prevent any additional errorCaptured hooks or app.config.errorHandler from being invoked for this error.

onRenderTracked()

Registers a debug hook to be called when a reactive dependency has been tracked by the component's render effect.

This hook is development-mode-only and not called during server-side rendering.

Type

function onRenderTracked(callback: DebuggerHook): void

type DebuggerHook = (e: DebuggerEvent) => void

type DebuggerEvent = {
  effect: ReactiveEffect
  target: object
  type: TrackOpTypes /* 'get' | 'has' | 'iterate' */
  key: any
}

See also: Reactivity in Depth

onRenderTriggered()

Registers a debug hook to be called when a reactive dependency triggers the component's render effect to be re-run.

This hook is development-mode-only and not called during server-side rendering.

Type

function onRenderTriggered(callback: DebuggerHook): void

type DebuggerHook = (e: DebuggerEvent) => void

type DebuggerEvent = {
  effect: ReactiveEffect
  target: object
  type: TriggerOpTypes /* 'set' | 'add' | 'delete' | 'clear' */
  key: any
  newValue?: any
  oldValue?: any
  oldTarget?: Map<any, any> | Set<any>
}

See also: Reactivity in Depth

onActivated()

Registers a callback to be called after the component instance is inserted into the DOM as part of a tree cached by <KeepAlive>.

This hook is not called during server-side rendering.

Type

function onActivated(callback: () => void): void

See also: Guide - Lifecycle of Cached Instance

onDeactivated()

Registers a callback to be called after the component instance is removed from the DOM as part of a tree cached by <KeepAlive>.

This hook is not called during server-side rendering.

Type

function onDeactivated(callback: () => void): void

See also: Guide - Lifecycle of Cached Instance

onServerPrefetch()

Registers an async function to be resolved before the component instance is to be rendered on the server.

Type

function onServerPrefetch(callback: () => Promise<any>): void

Details
If the callback returns a Promise, the server renderer will wait until the Promise is resolved before rendering the component.
This hook is only called during server-side rendering can be used to perform server-only data fetching.

Example

vue

<script setup>
import { ref, onServerPrefetch, onMounted } from 'vue'

const data = ref(null)

onServerPrefetch(async () => {
  // component is rendered as part of the initial request
  // pre-fetch data on server as it is faster than on the client
  data.value = await fetchOnServer(/* ... */)
})

onMounted(async () => {
  if (!data.value) {
    // if data is null on mount, it means the component
    // is dynamically rendered on the client. Perform a
    // client-side fetch instead.
    data.value = await fetchOnClient(/* ... */)
  }
})
</script>

See also: Server-Side Rendering

Edit this page on GitHub

Composition API: Lifecycle Hooks #

onMounted() #

onUpdated() #

onUnmounted() #

onBeforeMount() #

onBeforeUpdate() #

onBeforeUnmount() #

onErrorCaptured() #

onRenderTracked() #

onRenderTriggered() #

onActivated() #

onDeactivated() #

onServerPrefetch() #

Composition API: Lifecycle Hooks

onMounted()

onUpdated()

onUnmounted()

onBeforeMount()

onBeforeUpdate()

onBeforeUnmount()

onErrorCaptured()

onRenderTracked()

onRenderTriggered()

onActivated()

onDeactivated()

onServerPrefetch()