Hydration behavior in Vue - Step-by-Step Execution

Concept Flow - Hydration behavior

Server renders HTML

↓

Client loads page

↓

Vue attaches event listeners

↓

Vue reuses existing DOM

↓

Hydration completes

↓

App is interactive

Hydration is the process where Vue takes server-rendered HTML and makes it interactive by attaching event listeners and reusing the existing DOM.

Execution Sample

Vue

<template>
  <button @click="count++">Count: {{ count }}</button>
</template>
<script setup>
import { ref } from 'vue'
const count = ref(0)
</script>

A simple Vue component with a button that increments a count when clicked, demonstrating hydration of server-rendered HTML.

Execution Table

Step	Action	Client DOM State	Vue State	Result
1	Server renders static HTML with count=0	<button>Count: 0</button>	N/A	Static HTML sent to client
2	Client loads page and parses HTML	<button>Count: 0</button>	N/A	DOM exists but no Vue yet
3	Vue initializes and attaches to existing DOM	<button>Count: 0</button>	count=0	Vue state matches DOM content
4	Vue attaches event listener to button	<button>Count: 0</button>	count=0	Button is now interactive
5	User clicks button	<button>Count: 0</button>	count=0	Click event triggers count increment
6	Vue updates count to 1 and re-renders	<button>Count: 1</button>	count=1	DOM updates count text
7	User clicks button again	<button>Count: 1</button>	count=1	Click event triggers count increment
8	Vue updates count to 2 and re-renders	<button>Count: 2</button>	count=2	DOM updates count text
9	No more user interaction	<button>Count: 2</button>	count=2	App remains interactive
10	Page unload or navigation	<button>Count: 2</button>	count=2	Hydration session ends

💡 Hydration completes when Vue attaches to existing DOM and app becomes interactive.

Variable Tracker

Variable	Start	After Step 3	After Step 6	After Step 8	Final
count	undefined	0	1	2	2

Key Moments - 3 Insights

Why doesn't Vue recreate the entire DOM during hydration?

Vue reuses the existing server-rendered DOM to avoid unnecessary work and preserve the initial HTML, as shown in execution_table step 3.

What happens if the server HTML and Vue state don't match during hydration?

Vue will warn and may replace parts of the DOM to fix mismatches, but ideally they should match to avoid re-rendering, as implied in step 3 and 6.

When do event listeners get attached in hydration?

Event listeners are attached after Vue initializes on the client and reuses the DOM, as shown in step 4.

Visual Quiz - 3 Questions

Look at the execution_table, what is the value of 'count' after step 6?

A 2

B 0

C 1

D undefined

💡 Hint

Check the 'Vue State' column at step 6 in the execution_table.

At which step does Vue attach event listeners to the button?

A Step 2

B Step 4

C Step 3

D Step 5

💡 Hint

Look for the action describing event listener attachment in the execution_table.

If the server HTML showed 'Count: 5' but Vue state started at 0, what would happen during hydration?

A Vue would warn and update the DOM to match state

B Vue would ignore the mismatch and keep DOM as is

C Vue would crash and not hydrate

D Vue would reset state to 5 automatically

💡 Hint

Refer to the key moment about mismatches between server HTML and Vue state.

Concept Snapshot

Hydration behavior in Vue:
- Server renders static HTML
- Client loads and Vue attaches to existing DOM
- Vue reuses DOM and attaches event listeners
- State matches server HTML to avoid re-render
- After hydration, app is fully interactive
- Mismatches cause warnings and DOM updates

Full Transcript

Hydration in Vue means taking the HTML generated on the server and making it interactive on the client. First, the server sends static HTML with initial data. When the client loads the page, Vue attaches itself to the existing DOM instead of recreating it. Vue then attaches event listeners so the page responds to user actions. The Vue state must match the server HTML to avoid re-rendering. If the user clicks a button, Vue updates the state and changes the DOM accordingly. Hydration ends when Vue fully controls the page and it is interactive.

Practice

1. What is the main purpose of hydration in Vue when using server-side rendering?

easy

A. To connect the static HTML from the server with Vue's client-side code for interactivity

B. To generate HTML on the client without any server involvement

C. To replace all server-rendered HTML with new client-rendered HTML

D. To disable JavaScript on the client for faster loading

Solution

1. Step 1: Understand hydration concept

   Hydration links the server-rendered HTML with Vue's client code to make the page interactive without re-rendering everything.

2. Step 2: Compare options

   To connect the static HTML from the server with Vue's client-side code for interactivity correctly describes hydration. Options B, C, and D misunderstand hydration's role.

3. Final Answer:

   To connect the static HTML from the server with Vue's client-side code for interactivity -> Option A

4. Quick Check:

   Hydration = connect server HTML + client code [OK]

Hint: Hydration links server HTML to client Vue code [OK]

Common Mistakes:

• Thinking hydration generates HTML only on client
• Believing hydration replaces server HTML entirely
• Assuming hydration disables JavaScript

2. Which of the following Vue code snippets correctly enables hydration for a server-rendered app?

easy

A. createApp(App).mount('#app')

B. new Vue({ el: '#app' })

C. createSSRApp(App).mount('#app')

D. Vue.hydrate(App, '#app')

Solution

1. Step 1: Identify hydration method in Vue 3 SSR

   Vue 3 uses createSSRApp() to create an app that supports hydration of server-rendered HTML.

2. Step 2: Evaluate options

   createSSRApp(App).mount('#app') uses createSSRApp(). createApp(App).mount('#app') is for client-only apps. new Vue({ el: '#app' }) is Vue 2 syntax. Vue.hydrate(App, '#app') is invalid.

3. Final Answer:

   createSSRApp(App).mount('#app') -> Option C

4. Quick Check:

   SSR hydration uses createSSRApp() [OK]

Hint: Use createSSRApp() for hydration in Vue 3 SSR [OK]

Common Mistakes:

• Using createApp() instead of createSSRApp() for hydration
• Using Vue 2 syntax in Vue 3 projects
• Assuming Vue has a hydrate() method

3. Given this Vue 3 SSR hydration code snippet, what will be the console output?

const app = createSSRApp({
  data() { return { count: 0 } },
  mounted() { console.log('Mounted with count:', this.count) }
})
app.mount('#app')

medium

A. No output because mounted is not called during hydration

B. Mounted with count: 0

C. Error: createSSRApp is not a function

D. Mounted with count: undefined

Solution

1. Step 1: Understand mounted hook during hydration

   During hydration, the mounted hook runs after the client connects to server HTML, so it logs the current data state.

2. Step 2: Check data initialization

   Data count is initialized to 0, so the console logs 'Mounted with count: 0'.

3. Final Answer:

   Mounted with count: 0 -> Option B

4. Quick Check:

   Mounted logs count 0 during hydration [OK]

Hint: Mounted runs after hydration with initialized data [OK]

Common Mistakes:

• Thinking mounted does not run during hydration
• Assuming data is undefined at mount
• Confusing createSSRApp with createApp

4. You notice that after hydration, your Vue app's client-side interactivity is broken and console shows a mismatch warning. What is the most likely cause?

medium

A. The server-rendered HTML does not match the client-side template output

B. You forgot to import Vue in your client entry file

C. You used createApp() instead of createSSRApp() on the server

D. The mounted hook is missing in your component

Solution

1. Step 1: Understand hydration mismatch warning

   Vue warns when server HTML and client render output differ, causing hydration failure.

2. Step 2: Analyze options

   The server-rendered HTML does not match the client-side template output correctly identifies mismatch as cause. You forgot to import Vue in your client entry file causes import errors, not mismatch. You used createApp() instead of createSSRApp() on the server is about server setup, not client mismatch. The mounted hook is missing in your component does not cause hydration mismatch.

3. Final Answer:

   The server-rendered HTML does not match the client-side template output -> Option A

4. Quick Check:

   Mismatch = server HTML ≠ client template [OK]

Hint: Mismatch warning means server and client HTML differ [OK]

Common Mistakes:

• Ignoring mismatch warnings
• Confusing import errors with hydration issues
• Assuming missing mounted hook breaks hydration

5. You have a Vue 3 SSR app that renders a list of items on the server. Some items have a dynamic property that changes on the client only. How should you handle hydration to avoid mismatch errors?

hard

A. Ignore mismatch warnings since they don't affect user experience

B. Render all dynamic properties on the server to keep HTML identical

C. Disable hydration and fully re-render on client with createApp()

D. Use v-if or v-show to conditionally render client-only parts after hydration

Solution

1. Step 1: Identify client-only dynamic content issue

   Dynamic properties that differ between server and client cause hydration mismatches.

2. Step 2: Use conditional rendering for client-only parts

   Using v-if or v-show to render client-only content after hydration avoids mismatch.

3. Step 3: Evaluate other options

   Render all dynamic properties on the server to keep HTML identical is impractical if data is truly client-only. Disable hydration and fully re-render on client with createApp() disables hydration benefits. Ignore mismatch warnings since they don't affect user experience ignores errors.

4. Final Answer:

   Use v-if or v-show to conditionally render client-only parts after hydration -> Option D

5. Quick Check:

   Client-only content = conditional render after hydration [OK]

Hint: Render client-only parts conditionally after hydration [OK]

Common Mistakes:

• Trying to render client-only data on server
• Disabling hydration unnecessarily
• Ignoring mismatch warnings