Skip to content
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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

tomhughes
Copy link
Member

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:

@gravitystorm
Copy link
Collaborator

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).

@tomhughes
Copy link
Member Author

We certainly have statistics.. Here's some for yesterday for Chrome:

Label Unique visitors Visits Actions
Chrome 109.0 1348 1638 3661
Chrome 111.0 240 242 445
Chrome 116.0 182 203 303
Chrome 117.0 210 223 268
Chrome 119.0 134 186 409
Chrome 120.0 306 524 1128
Chrome 122.0 346 402 734
Chrome 124.0 197 235 489
Chrome 125.0 299 479 1054
Chrome 126.0 272 304 569
Chrome 127.0 227 270 635
Chrome 128.0 628 692 1154
Chrome 129.0 412 487 1124
Chrome 130.0 2034 2645 5508
Chrome 131.0 42248 54074 130543

and Firefox:

Label Unique visitors Visits Actions
Firefox 112.0 161 165 285
Firefox 115.0 656 778 1203
Firefox 128.0 1054 1336 2694
Firefox 132.0 256 333 926
Firefox 133.0 8128 10528 22041

and Edge:

Label Unique visitors Visits Actions
Microsoft Edge 122.0 669 673 783
Microsoft Edge 130.0 535 634 988
Microsoft Edge 131.0 15644 18433 34458
Microsoft Edge 133.0 2557 2566 3230

and Safari:

Label Unique visitors Visits Actions
Safari 15.6 327 362 513
Safari 16.6 462 497 756
Safari 17.4 213 243 406
Safari 17.5 347 405 711
Safari 17.6 1104 1256 2140
Safari 17.8 324 350 460
Safari 18.0 284 338 784
Safari 18.1 2968 3358 5974
Safari 18.2 1055 1203 2709

and Chrome Mobile:

Label Unique visitors Visits Actions
Chrome Mobile 87.0 164 189 319
Chrome Mobile 103.0 193 226 308
Chrome Mobile 111.0 303 340 412
Chrome Mobile 117.0 195 219 383
Chrome Mobile 118.0 249 281 337
Chrome Mobile 119.0 294 315 430
Chrome Mobile 120.0 304 329 505
Chrome Mobile 123.0 169 187 231
Chrome Mobile 124.0 198 213 285
Chrome Mobile 125.0 205 221 278
Chrome Mobile 126.0 691 760 1066
Chrome Mobile 127.0 461 513 692
Chrome Mobile 128.0 364 405 597
Chrome Mobile 129.0 627 709 1097
Chrome Mobile 130.0 1213 1373 2000
Chrome Mobile 131.0 40778 44943 63056

and Chrome Webview:

Label Unique visitors Visits Actions
Chrome Webview 92.0 373 460 900
Chrome Webview 114.0 205 262 680
Chrome Webview 131.0 5769 6362 11833

and Mobile Safari:

Label Unique visitors Visits Actions
Mobile Safari 15.6 1086 1232 1688
Mobile Safari 16.0 191 215 250
Mobile Safari 16.1 497 543 690
Mobile Safari 16.2 411 447 548
Mobile Safari 16.3 349 385 499
Mobile Safari 16.5 149 166 198
Mobile Safari 16.6 1985 2218 2771
Mobile Safari 17.1 187 207 259
Mobile Safari 17.2 309 335 403
Mobile Safari 17.3 259 286 341
Mobile Safari 17.4 414 466 546
Mobile Safari 17.5 1490 1638 1946
Mobile Safari 17.6 4076 4458 5433
Mobile Safari 17.7 373 402 479
Mobile Safari 17.8 431 489 573
Mobile Safari 18.0 1669 1856 2299
Mobile Safari 18.1 22432 24657 30253
Mobile Safari 18.2 4024 4550 6164

@tomhughes
Copy link
Member Author

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?

@HolgerJeromin
Copy link
Contributor

missing 2023 in firefox
https://caniuse.com/mdn-javascript_builtins_weakmap_symbol_as_keys

Is a quite esotheric feature. But really needed stuff was not added in 2023. So fine with going with 2022.

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.

This feels more critical as it is. The browsers are implementing features years before the spec is published.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants