More specific data types - ArrayBuffer instead of ArrayBufferLike #279
+5
−5
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, TypeScript interfaces like
DataView
andUint8Array
are used with the more genericArrayBufferLike
type, representing that they can work with eitherArrayBuffer
orSharedArrayBuffer
. TypeScript 5.9 now uses stricter types for interfaces such as the DOMfetch
method: a DOMBufferSource
is now (correctly) marked as requiringArrayBuffer
, notSharedArrayBuffer
. As a result of that change, trying to use a @msgpack/msgpackencode
result with afetch
call will result in a type error. This change updates the types in theEncoder
class to useArrayBuffer
instead ofArrayBufferLike
, which reflects their implementation and prevents issues with the newer, stricter interfaces.See microsoft/TypeScript#62168 for more info.