Release version v3.34.3

• An AbortSignal already aborted when ZipWriter#add() or Entry#getData() is called now rejects the call. The signal was only handed to pipeTo(), which ignores it on the engines below its support floor, i.e. the oldest browsers the test matrix covers: the whole entry was then written and there was nothing left to abort. Both methods now check the signal before starting, and reject with signal.reason when it is set, so the error is unchanged on the engines that already honored it, or with an AbortError whose message is ERR_ABORTED otherwise, signal.reason not existing before Chrome 98. A pre-aborted add() also rejects before the temporary stream of a buffered entry is created, so nothing is allocated to dispose
• The chunks of a ZipReaderStream now expose the properties deposited on an entry while its data is read, i.e. EntryMetaData#warnings and EntryMetaData#localDirectory. The chunk was built from a copy of the entry taken before the read started, so those two were permanently absent from it, and the warnings channel added in v2.8.x was unreachable from ZipReaderStream although the types promise it. The chunk now shares them with the entry, so they are readable on it once its readable property has been consumed
• BlobReader no longer fails with sourceBlob.stream is not a function when its source is a Blob-like object exposing only size, slice and arrayBuffer. It reads with stream() when the source has it and falls back to the slice()/arrayBuffer() path otherwise, which the reader already implemented for the engines whose Blob#slice is unreliable

• The signal option of the reader and of the writer documents that a signal already aborted rejects the call, and with which error

• New test covering a signal already aborted when add() and getData() are called, with and without a reason, registered without the pipeToSignal feature gate so that it runs on the engines the fix is for
• New test covering a BlobReader over a source without stream()
• The warnings test asserts that a ZipReaderStream chunk carries the local directory and the warnings of its entry
• The temporary stream test no longer uses a pre-aborted signal to reach its error path, which no longer creates a temporary stream, and covers a failing Reader instead; a second case pins that a pre-aborted add() creates none

• #1260 4a0adf3 - Recover the bottom pin when the browser clamps an end-anchored scroll compensation write. resizeItem compensates a size change by writing scrollTop before the consumer has committed the new total size, so when the grown item does not itself extend the scroll range the browser clamps the write to the old maximum and the viewport is left short of the end with no scroll event to correct it. Two cases hit this: paddingEnd > 0 with a growing last item, where the overflowing item only extends scrollHeight to its own end and the clamp lands exactly paddingEnd short (#1258); and a row above the last one growing while the last row keeps its size, under directDomUpdates (#1266). A compensation write whose target exceeds the scroll maximum at write time is now recorded as clamped and re-issued once the sizer has grown — right after notify for consumers that size the container synchronously in onChange, and from _willUpdate for consumers that size it during a render. The clamped read-back keeps the retry pending; any other scroll event cancels it, so a user reading history is never yanked.

• Updated dependencies [4a0adf3]:
  • @tanstack/virtual-core@3.17.9

• Updated dependencies [4a0adf3]:
  • @tanstack/virtual-core@3.17.9

• Updated dependencies [4a0adf3]:
  • @tanstack/virtual-core@3.17.9

• #1264 bb4e0f1 - Re-export @tanstack/virtual-core from @tanstack/lit-virtual, so the core API (Virtualizer, defaultRangeExtractor, measureElement, the scroll observers and the shared types) can be imported from the adapter without adding @tanstack/virtual-core as a second dependency. Every other framework adapter already does this.

• Updated dependencies [4a0adf3]:
  • @tanstack/virtual-core@3.17.9

• Updated dependencies [4a0adf3]:
  • @tanstack/virtual-core@3.17.9

• Updated dependencies [4a0adf3]:
  • @tanstack/virtual-core@3.17.9

• Updated dependencies [4a0adf3]:
  • @tanstack/virtual-core@3.17.9