Hydration behavior in Angular - Step-by-Step Execution

Concept Flow - Hydration behavior

Server renders HTML

↓

Browser loads HTML

↓

Angular bootstraps app

↓

Hydration: Attach event listeners

↓

App becomes interactive

↓

User interacts with app

Hydration is the process where Angular attaches its logic to server-rendered HTML to make the app interactive in the browser.

Execution Sample

Angular

import { bootstrapApplication } from '@angular/platform-browser';
import { provideClientHydration } from '@angular/platform-browser';

bootstrapApplication(AppComponent, {
  providers: [provideClientHydration()]
});

This code boots the Angular app with hydration enabled to attach logic to server-rendered HTML.

Execution Table

Step	Action	State Before	State After	Effect
1	Server renders HTML	No HTML in browser	Static HTML present	Page visible but not interactive
2	Browser loads HTML	Static HTML present	Static HTML present	Page displayed to user
3	Angular bootstraps app	Static HTML present	Angular app initialized	Angular ready to hydrate
4	Hydration attaches event listeners	Angular app initialized	Event listeners attached	Page becomes interactive
5	User interacts	Page interactive	State updates on interaction	UI responds to user actions
6	Exit	App interactive	No further hydration needed	Hydration complete

💡 Hydration ends after event listeners attach and app is interactive

Variable Tracker

Variable	Start	After Step 3	After Step 4	Final
HTML	None	Static HTML loaded	Static HTML loaded	Static HTML loaded
Angular App	Not bootstrapped	Bootstrapped	Bootstrapped	Bootstrapped
Event Listeners	None	None	Attached	Attached
Interactivity	No	No	Yes	Yes

Key Moments - 3 Insights

Why does the page show content before Angular starts?

Because the server sends fully rendered HTML first (see execution_table step 1 and 2), so the user sees content immediately before hydration.

What exactly does hydration do in Angular?

Hydration attaches event listeners and Angular logic to the existing HTML without re-rendering it (see execution_table step 4).

Does hydration re-render the whole page?

No, hydration only attaches behavior to the existing HTML, so the page is not re-rendered (see variable_tracker Event Listeners and HTML rows).

Visual Quiz - 3 Questions

Look at the execution table, at which step do event listeners get attached?

A Step 2

B Step 3

C Step 4

D Step 5

💡 Hint

Check the 'Action' column for when event listeners are attached.

According to the variable tracker, when does interactivity become 'Yes'?

A After Step 3

B After Step 4

C At Start

D After Step 2

💡 Hint

Look at the 'Interactivity' row and see when it changes to 'Yes'.

If Angular did not hydrate, what would the 'Interactivity' variable be after Step 4?

A No

B Yes

C Undefined

D Bootstrapped

💡 Hint

Refer to variable_tracker and understand hydration's role in enabling interactivity.

Concept Snapshot

Hydration behavior in Angular:
- Server sends fully rendered HTML.
- Browser loads static HTML immediately.
- Angular bootstraps and attaches event listeners.
- Hydration makes the page interactive without re-rendering.
- User can interact with the app seamlessly.

Full Transcript

Hydration in Angular means the server sends a fully rendered HTML page first. The browser shows this static content immediately. Then Angular starts up in the browser and attaches event listeners and logic to the existing HTML. This process is called hydration. It makes the page interactive without rebuilding the whole page. The user sees content fast and can interact smoothly once hydration finishes.