The Perils of Hydration: Understanding how Gatsby/Next manage server-side rendering and hydration Introduction I ran into the strangest issue recently. In production, the bottom of my blog was doing something… unintended: A bit of digging into the Elements tab in the devtools revealed the culprit… My React component was rendering in the wrong spot.
Table of contents
IntroductionLink to this heading Some problematic codeLink to this heading Server-side rendering 101Link to this heading Dynamic sectionsLink to this heading Hydration ≠ renderLink to this heading The solutionLink to this heading Two-pass renderingLink to this heading AbstractionsLink to this heading Mental modelsSort: