Releases: jsdom/webidl-conversions
7.0.0
Bumped Node.js version requirement to ≥12.
Removed Function
and VoidFunction
exports. These are better handled by webidl2js
.
Renamed the void
export to undefined
, per Web IDL spec updates.
Added support for environments without SharedArrayBuffer
.
Fixed a typo in one of the exception messages for BufferSource
. (@ExE-Boss)
6.1.0
Version 6.0.0
Bumped Node.js version requirement to ≥10.4.
Added support for throwing exception objects that belong to a different realm than the current.
Improved the accuracy of unsigned long long
and long long
conversions by using BigInt
.
Made TypedArray conversions unforgeable. (@ExE-Boss)
Fixed object
conversion so that it throws on BigInt values.
5.0.0
Removed the Error
export, as the type was removed from Web IDL.
Raised the minimum supported version to Node v8.
Fixed all buffer source type conversions to be realm-independent, i.e. they will no longer throw if given buffer source objects from other realms.
4.0.2
4.0.1
(This release should have been 4.1.0; oops.)
- Added the ability to pass context information in to be used in error messages.
- Fixed
ByteString
andUSVString
to not acceptSymbol
values - Fixed integer types to never return
-0
. - Fixed integer types to round correctly for negative numbers.
4.0.0
This release welcomes @TimothyGu, who implemented all of the remaining basic Web IDL types and some bonus ones.
- Added:
any
,object
,Error
, buffer source types, and "common definitions" - Removed (because they were removed from the Web IDL spec):
Date
,RegExp
- Fixed:
unrestricted double
to properly allowNaN
float
andunrestricted float
to properly truncate into 32-bit floating pointsDOMString
, to throw an error forSymbol
s- integer types, in various ways
This release also adds test coverage for all conversions! This should help especially with the pesky integer types and the continual bugs we've seen around them.