arturovt c04931c88b fix(core): throw a descriptive error instead of crashing when a hydration node is missing ...

locateOrCreateElementNodeImpl looks up the DOM node for an element
during hydration and immediately checks its nodeType. If the
client-rendered DOM has fewer nodes than the server-rendered HTML,
the lookup returns null, and in production that null flows straight
into the nodeType check and crashes with a raw, uncoded
"Cannot read properties of null (reading 'nodeType')" TypeError.

The dev-mode check that would normally catch this (validateMatchingNode)
already handles a missing node, but it's compiled out of production
builds, so the crash only shows up outside of dev mode.

Add a null check ahead of the nodeType check that throws a coded
RuntimeError using the existing HYDRATION_MISSING_NODE (NG0502) code,
with a descriptive message in dev mode and a cheap fallback in
production. Also add a regression test that removes a server-rendered
element before hydration runs and asserts a coded RuntimeError is
thrown instead of a raw TypeError.

(cherry picked from commit c6e4a36be1)

2026-08-14 15:30:53 +00:00

..

init

build: consolidate domino bundling in platform-server

2026-03-25 13:31:05 -07:00

src

docs(platform-server): add error reference page for NG05703 and wire up RuntimeError

2026-07-09 11:56:01 -07:00

test

fix(core): throw a descriptive error instead of crashing when a hydration node is missing

2026-08-14 15:30:53 +00:00

testing

…

third_party/domino

build: consolidate domino bundling in platform-server

2026-03-25 13:31:05 -07:00

BUILD.bazel

build: cleanup workspace deps

2026-04-23 11:38:26 -07:00

index.ts

…

package.json

build: update minimum supported Node.js versions

2026-05-27 10:39:17 -07:00

PACKAGE.md

…

public_api.ts

…