Open source work

postTask() returned Promise<any>, so the type of the callback’s result was lost. It is now generic, and an async callback resolves to the awaited value.

Original title: Make Scheduler.postTask generic over the callback result

createElementNS with the XHTML namespace returns the specific element type, like HTMLDivElement for "div", as SVG and MathML already do.

Original title: Add a generic createElementNS overload for the XHTML namespace

Calling observe(target) without options always throws at runtime. The DOM types now flag it at compile time.

Original title: Make options required in MutationObserver.observe()

Batch size and receive timeout can be set per listener, with SpEL and property placeholders.

Original title: Add batchSize and batchReceiveTimeout to @RabbitListener

Documents that channel pools are bounded and block when exhausted, and that the factory is not meant for consumers.

Original title: Document PooledChannelConnectionFactory sizing

A memory created with shared: true exposes a SharedArrayBuffer, but lib.dom said ArrayBuffer, so instanceof SharedArrayBuffer checks narrowed to never. Memory is now generic over its buffer type, and existing code keeps working.

Original title: Type WebAssembly.Memory buffers as ArrayBufferLike for shared memories

Explains the TS2882 error on CSS imports since TypeScript 6.0, with fixes for library authors and for users.

Original title: Document noUncheckedSideEffectImports fixes for CSS packages

Offered to implement the proposed ErrorConstructorStatics split and flagged a compatibility risk first: @types/node statics such as captureStackTrace would stop reaching TypeError, reproduced as TS2339.

Original title: InstanceType and constructor return type inference for built-in Error subtypes

Reported that #2578 now makes observe(target) without options a compile-time error, and laid out what remains: options like {} still need a union type that would break existing code.

Original title: MutationObserver.observe options should not be optional (follow-up)

Proposed typing the receive side as ReadableStream<Uint8Array<ArrayBuffer>> and the send side as WritableStream<BufferSource>, matching how other byte streams are typed and what WPT covers.

Original title: Missing bounds in WebTransportReceiveStream and WebTransportSendStream parent types

Showed that the proposed definition rejects an explicit undefined under exactOptionalPropertyTypes, which type-fest itself enables, and suggested adding undefined with a type test for both settings.

Original title: Nullish / Nilable type

Showed the request can already be expressed with Paths (leavesOnly) and Get, and listed the questions a dedicated type would need to answer: leaves only, arrays and tuples, recursion depth.

Original title: DeepValuesOf

Helped the reporter toward a fix: traced why static methods are excluded from the Iterable overloads (the generator filters them since #1839) and compared two approaches for TypeScript 6+.

Original title: AbortSignal.any should accept an Iterable<AbortSignal>

Explained that overload choice depends on the order of the checker passes, not the order of the overloads: resolveCall tries every overload with the subtype relation before falling back to assignability.

Original title: Why is the 2nd overload picked up?