browserl.ist returns incorrect Edge versions

[iamdavidcz]

Steps to reproduce:

1. Go to this page: https://browserl.ist/?q=last+2+Edge+versions

Current behaviour:

It returns Edge versions 18 and 17

Expected behaviour:

It should return Edge versions 83 and 81
See https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel

Edit:
From command line it works fine:

$ npx browserslist "last 2 Edge versions"
edge 83
edge 81

[ai]

We are collecting funds for free big and important refactorings in Browserslist ecosystem including website.

https://opencollective.com/browserslist

[aceHubert]

same error

[ai]

@aceHubert you can talk to your company about sponsoring Browserslist. Right now I spend all my free time for PostCSS 8 release.

https://opencollective.com/browserslist

[ylemkimon]

browserl.ist has been broken since Vercel (formerly ZEIT now) no longer supports server apps. However, I came across another project: https://browserslist.dev/ (https://github.com/PSPDFKit-labs/browserslist.dev), which uses more recent version. I'm not sure about its status nor whether it'll be updated regularly.

[ritz078]

@ylemkimon I am from the development team of https://browserslist.dev. We also use it to show the browsers we support for every version of PSPDFKit so we plan to always keep it updated.

[iamdavidcz]

CLI tool returns incorrect versions as well:

$ npx browserslist "last 2 Edge versions"
edge 84
edge 83

Tested on version 4.14.2:

$ npx browserslist --version
browserslist 4.14.2

It should return Edge versions 85 and 84.
See: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel

[ylemkimon]

@iamdavidcz browserslist relies on the Can I use data, which doesn't include Edge 85 yet. You should open the issue at https://github.com/fyrd/caniuse/issues.

[isvladxxe]

All old CI expected behaviour 17, 18, but now it is broken.
My colleagues from the previous project contacted me about this issue.

no matter how much I dislike to support edgeHtml, there are platforms that are never updated to edge chromium (like vin7, it etc) which are, for example, in offices or universities where they have no rights to install software, and sometimes there really are no system administrators (post ussr location)
it is expected that the EdgeHtml engine will be used and with the arrival of security updates it will be updated and the CI will work
"edge chromium" needs new separate tag
or
EdgeHtml needs its own

[masi]

I was also wondering if a LegacyEdge name wouldn't make rules easier.