Patch Changes
-
#3557
e6da1fdThanks @DylanPiercey! - Route a failed lazy input-signal chunk load to the surrounding<try>@catchboundary. Previously, when a lazy tag's input chunk rejected on its own (a network-level partial failure, e.g. deploy skew) while its setup chunk resolved, the branch was cloned but never inserted: the@placeholderstayed shown forever and@catchnever fired. The rejection now drives the same boundary as a setup failure. -
#3570
e91efd4Thanks @DylanPiercey! - FixMap/Setserialization silently dropping (Set) or corrupting (Map) a member that references an ancestor object — e.g. a back-reference or undirected-graph edge. Such members are now inserted after construction so the resumed collection is intact. -
#3571
ee882c8Thanks @DylanPiercey! - SerializeDataViewso it can be read from content that updates in the browser. ADataViewor typed array over a buffer that cannot be serialized (e.g.SharedArrayBuffer) is now reported as unserializable instead of emitting a malformed constructor call that broke the whole payload. -
#3566
909d56dThanks @DylanPiercey! - SerializeIntlformatters andIntl.Localeso they can be read from content that updates in the browser, instead of failing to serialize. Formatters are rebuilt fromresolvedOptions(); note thatIntl.DateTimeFormatreports a resolvedmonth/weekdaywidth that can differ from the requested one in some locales (ja,zh), so a rebuilt formatter may render those fields differently than the server did. -
#3568
09ee04bThanks @DylanPiercey! - SerializeTemporalvalues so they can be read from content that updates in the browser. Each type is rebuilt from its own string form, preserving calendar and time zone annotations along with nanosecond precision. -
#3578
952dcaeThanks @DylanPiercey! - Fixtemplate.render()'s async iterator (for await) silently dropping HTML chunks — truncating the streamed document with no error — when the consumer took longer than a flush tick between reads. Buffered chunks are now retained until the consumer reads them. -
#3566
f0ff1bfThanks @DylanPiercey! - Say why a value is being serialized in theUnable to serializedevelopment error, so it reads as a requirement on values the browser references rather than an arbitrary restriction.