Keep-alive for expensive components in Vue - Step-by-Step Execution

Concept Flow - Keep-alive for expensive components

Component mounts first time

↓

Component renders and runs setup

↓

Component cached by <keep-alive>

↓

User navigates away

↓

Component is hidden but state kept

↓

User navigates back

↓

Component restored from cache, no re-setup

↓

Component continues with preserved state

This flow shows how Vue's <keep-alive> caches a component after first render, preserving its state when hidden and restoring it without re-running setup.

Execution Sample

Vue

<template>
  <keep-alive>
    <ExpensiveComponent v-if="show" />
  </keep-alive>
  <button @click="show = !show">Toggle</button>
</template>

<script setup>
import { ref } from 'vue'
import ExpensiveComponent from './ExpensiveComponent.vue'
const show = ref(true)
</script>

This Vue code toggles an expensive component inside <keep-alive>, caching it to avoid re-setup on toggle.

Execution Table

Step	Action	Component State	Cache Status	Rendered Output
1	Initial render, show=true	ExpensiveComponent setup runs	Cache empty	ExpensiveComponent visible
2	User clicks toggle, show=false	ExpensiveComponent hidden but alive	Component cached	No component visible
3	User clicks toggle, show=true	ExpensiveComponent restored from cache	Component cached	ExpensiveComponent visible with preserved state
4	User clicks toggle, show=false again	Component hidden, state preserved	Component cached	No component visible
5	User clicks toggle, show=true again	Component restored, no setup rerun	Component cached	ExpensiveComponent visible with same state
6	User navigates away, component unmounted	Component destroyed	Cache cleared if <keep-alive> removed	No component visible

💡 Execution stops when component is unmounted or <keep-alive> removed, clearing cache.

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	After Step 5	After Step 6
show	true	true	false	true	false	true	false
ExpensiveComponent state	none	initialized	preserved (hidden)	restored	preserved (hidden)	restored	destroyed
Cache	empty	stores component	stores component	stores component	stores component	stores component	cleared

Key Moments - 3 Insights

Why doesn't ExpensiveComponent run setup again when toggled back on?

Because <keep-alive> caches the component after first mount (see Step 3 in execution_table), so it restores the component from cache without rerunning setup.

What happens to the component state when it is hidden by v-if inside <keep-alive>?

The component is hidden but kept alive and its state is preserved in cache (see Step 2 and Step 4), so when shown again, it resumes with the same state.

When is the cached component destroyed and removed from memory?

When the component is unmounted or <keep-alive> is removed from the template (see Step 6), the cache clears and the component is destroyed.

Visual Quiz - 3 Questions

Look at the execution_table, what is the cache status after the user first hides the component (Step 2)?

A Cache cleared

B Cache empty

C Component cached

D Component destroyed

💡 Hint

Check the 'Cache Status' column at Step 2 in the execution_table.

At which step does the ExpensiveComponent restore from cache without running setup again?

A Step 1

B Step 3

C Step 6

D Step 2

💡 Hint

Look at the 'Component State' column describing setup or restore in the execution_table.

If the <keep-alive> wrapper is removed, what happens to the component when toggled off?

A Component is destroyed and state lost

B Component is hidden but state preserved

C Component is cached and preserved

D Component setup runs again immediately

💡 Hint

Refer to Step 6 and the explanation about cache clearing when is removed.

Concept Snapshot

Vue <keep-alive> caches components to preserve state.
Wrap expensive components with <keep-alive>.
When toggled off, component is hidden but kept alive.
When toggled on again, component restores without re-setup.
Cache clears only when component unmounts or <keep-alive> removed.

Full Transcript

This visual execution shows how Vue's <keep-alive> works to cache expensive components. Initially, the component mounts and runs its setup. When the user hides it using v-if, the component is not destroyed but hidden and cached. Later, when shown again, the component restores from cache without running setup again, preserving its state. The cache remains until the component is unmounted or <keep-alive> is removed, at which point the component is destroyed and cache cleared. This helps improve performance by avoiding repeated expensive setup work.