Hydration
Hydration connects browser behavior and state to HTML that a server or build already made. This turns chosen parts of the page into interactive controls.
Another example
A server sends product cards with one cart control. Only the cart area loads JavaScript and keeps the DOM already on the page. Making all HTML inside the browser is client rendering, not hydration.
Main parts
- 01server-rendered markup
- 02client module
- 03state attachment
Use it when
Use this term when browser behavior is attached to HTML that is already rendered.
Do not use it when
Do not hydrate static content that has no browser interaction or changing state.
Name used in code
rendered HTML + client module → interactive island Before you ship
Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback.
Outcome: Use or review Hydration as a technical building block that the team can maintain. User context: A server sends product cards with one cart control. Only the cart area loads JavaScript and keeps the DOM already on the page. Making all HTML inside the browser is client rendering, not hydration. Technology or engineering concept: Hydration. Why it fits: Use this term when browser behavior is attached to HTML that is already rendered. Do not use it when: Do not hydrate static content that has no browser interaction or changing state. Engineering fit: Define where it runs and which version to use. Set its job, interfaces, data flow, dependencies, supported systems, security, and speed limits. Explain how it fits the current stack. Lifecycle safeguards: Check dependency health and licenses. Add monitoring and a fallback. Name the upgrade owner. Do not add a second tool for the same job without a measured benefit. Acceptance criteria: A small integration proves the needed behavior. Test compatibility, security, failure, and performance. Document deploy, upgrade, support, and rollback steps. Evidence and limits (evidence boundary): No single official standard controls the whole term. Its meaning may change across teams, platforms, or frameworks. Unknowns to confirm: Current stack, runtime and version rules, target systems, dependency owner, performance budget, support period, and migration limits.
Check this request
Review the current use of Hydration. Definition: Hydration connects browser behavior and state to HTML that a server or build already made. This turns chosen parts of the page into interactive controls. Release checks: Check the runtime and version, integration limits, dependencies and licenses, and platform support. Verify security, failure, speed, monitoring, deploy, support owner, upgrade path, and rollback. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.