Do not install C++ streams when ts flag is on
Modified installation behavior of C++ streams based on the ts flag.
23 substantial PRs (23 merged, 7 open/draft). 3 in node, 20 in workerd.
Modified installation behavior of C++ streams based on the ts flag.
Added support for running fetch wpt's with and without ts streams.
Optimize TS streams strategy by reading highWaterMark only once
Update TS streams bridge to start native source pull or sink write before marking it in flight
Fix issue with TS compression write or close being cut short by a cancel
Update TextDecoderStream to accept bare SharedArrayBuffer chunks, aligning with Node and the Encoding Standard.
Fix IdentityTransformStream to treat undefined chunks as no-op writes and improve options handling.
Improve handling of detached native writable streams by closing them and rejecting pending writes.
Replace rough utf8 length estimation with precise length counting for accurate backpressure signaling.
Address algorithm clearance and re-entrancy issues to improve stability and security.
Updated comment for writableFloatQueueTotal to accurately reflect spec double arithmetic
Fixed tee branch close re-entrancy bugs
Clamped TS readable queue total at dequeue to match spec behavior
Updated TS ReadableStream.from to follow spec's iterator protocol
Updated the TS ReadableStream async iterator to match WebIDL specifications, including changes to next() and return() methods
Pinned SharedArrayBuffer view rejection across byte-stream entry points to reject with a TypeError
Tuned re-entrancy and microtask resolution timing to prevent user code from running in internal paths
Improved the performance of util.MIMEType parsing, making it about twice as fast as undici's handrolled version.
Applied a batch of stream/iter fixes and improvements for performance and conformance
Adds an async trace internal mechanism to help evaluate API optimizations
Introduces a new bench mechanism for benchmarks, similar to wd-test
Adds perfetto support for Rust
Implements a structured logging API with a provider model, including four built-in providers