BREAKING CHANGES:

Dropped support for Node <18.20.0, because Import Assertions has been replaced by Import Attributes.

v2.3.0...v3.0.0

Assets 2

30 Aug 12:59

wessberg

v2.3.0

4250e7d

v2.3.0

feat: remove and_qq, and_uc, baidu, and kaios from generated browserslists, as the data for these browsers are lacking and harms feature detection otherwise ac24451
feat: allow more precise filtering 553c111

v2.2.0...v2.3.0

Assets 2

30 Aug 11:17

wessberg

v2.2.0

499e019

v2.2.0

chore: bump rollup-plugin-ts dep 2cf5285
feat: add support for ES2024 7b3c548

v2.1.0...v2.2.0

Assets 2

02 Aug 23:20

wessberg

v2.1.0

e1d7131

v2.1.0

feat: add ES2023 support 80d81a4

v2.0.3...v2.1.0

Assets 2

02 Feb 12:56

wessberg

v2.0.3

397fcb2

v2.0.3

fix: point to new feature name for nullish coalescing assignments in mdn compat data af2b4ca

v2.0.2...v2.0.3

Assets 2

23 Jan 20:58

wessberg

v2.0.2

a9f128c

v2.0.2

feat: handle Android browsers even better f28918f

v2.0.1...v2.0.2

Assets 2

20 Jan 15:52

wessberg

v2.0.1

cfe21b8

v2.0.1

New Features

`browserslist-generator` is now based on ESM and requires Node v14.19.0 (BREAKING CHANGE)

Now is a good time to make browserslist-generator a type: "module" package. However, it still provides a CommonJS fallback. If your codebase is still based on CommonJS, you should be fine. Please know however, that browserslist-generator requires an environment running Node v14.19.0 or newer going forward.