- Updated dependencies, base files, and editions using boundation
- Thank you to the sponsors: Andrew Nesbitt, Balsa, Codecov, Poonacha Medappa, Rob Morris, Sentry, Syntax
- Updated dependencies, base files, and editions using boundation
- Thank you to the sponsors: Andrew Nesbitt, Balsa, Codecov, Poonacha Medappa, Rob Morris, Sentry, Syntax
- Updated dependencies, base files, and editions using boundation
- Updated dependencies, base files, and editions using boundation
- Updated dependencies, base files, and editions using boundation
- Updated dependencies, base files, and editions using boundation
- Updated dependencies, base files, and editions using boundation
- Updated dependencies, base files, and editions using boundation
- Updated dependencies, base files, and editions using boundation
- Updated license from
MITtoArtistic-2.0 - Minimum required node version changed from
node: >=10tonode: >=18to keep up with mandatory ecosystem changes - No longer uses
node-fetch, instead uses the Node.jsfetchbuiltin - Changed default threshold to 85% to support ES2018 with Node.js 14
- Updated dependencies, base files, and editions using boundation
- Updated dependencies, base files, and editions using boundation
- Updated dependencies, base files, and editions using boundation
- Fixed the functionality of
v4.2.1for its intended use case
- For the simpler API methods, it now supports a fallback return pre-seeded by a specified ECMAScript version (defaults to
ES5) for when the API is inaccessible or the Node.js release has not yet had data added for it, such as Node.js v0.8.x.
- Now supports significant Node.js version numbers, such as
12or0.12
- Prior
fetchExclusiveCompatibleESVersionsForNodeVersionsis nowfetchAllCompatibleESVersionsForNodeVersions fetchExclusiveCompatibleESVersionsForNodeVersionsnow only returns the minimum amount of ECMAScript versions that are required to support the specified Node.js releases, which was its intent
- Same API, however additional properties and methods for simplifying the identification of which ECMAScript versions are actually compatible
- Now explicit about what version is what
- Now includes the information of the versions in each ECMAScript version compatibility result for simplicity
- Initial working release