-
Notifications
You must be signed in to change notification settings - Fork 923
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump allowed ECMAScript version to 2022 (ES13) #5421
base: master
Are you sure you want to change the base?
Conversation
Does the OSMF have any stats about what percentage of visitors to the website this would affect? I'm assuming that there's going to a be a proportion of people using browsers that don't support ECMAScript 2022 since that's only a couple of years old. My guess would include older Android devices, for example, which are often used beyond their software support lifecycle. I'd lean towards being cautious, unless there's a compelling reason to update (e.g. major dependencies that we don't control). |
We certainly have statistics.. Here's some for yesterday for Chrome:
and Firefox:
and Edge:
and Safari:
and Chrome Mobile:
and Chrome Webview:
and Mobile Safari:
|
Looks like there is one feature in 2022 that is an issue for Safari 15 and the Chrome 87/92 outliers are also a bit more limited but of the rest is OK I think? |
missing 2023 in firefox Is a quite esotheric feature. But really needed stuff was not added in 2023. So fine with going with 2022.
This feels more critical as it is. The browsers are implementing features years before the spec is published. |
We've been on 2015 for a long time as we no longer care about IE there's probably no good reason not to bump it.
I've had a look at the support matrices and up to 2022 just about everything seems to be supported in all current browsers. Detailed results can be found:
There is at least one 2023 feature that isn't fully supported yet: