[openstreetmap/openstreetmap-website] Bump allowed ECMAScript version to 2022 (ES13) (PR #5421)

[Andy Allan]

> 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?

That's how I'm reading it too. I'm not sure why some people might be on those old versions, my guess is that upgrades are blocked by needing a phone OS upgrade, or something similar. Perhaps it's some people can't afford a hardware upgrade.

The not-fully-supported browser versions (including Safari up to 16.3) total to 1.9% of unique visitors, which is higher than I expected when I first glanced at the numbers. I can't comment on how likely it is that we will write code that using unsupported features, or that eslint will suggest changes that make the code incompatible with that 1.9% of visitors. Maybe this is all a theoretical problem, but I'd like to avoid breaking the site, unless there's a significant benefit for other users or compelling benefits for devs.

I note that ECMAScript 2021 seems to be fully supported across all the mentioned browser versions. So should we target that version instead?

> The browsers are implementing features years before the spec is published.

Interesting, I didn't know that. Thanks for the info.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/5421#issuecomment-2593265822
You are receiving this because you are subscribed to this thread.

Message ID: <openstreetmap/openstreetmap-website/pull/5421/c2593265822 at github.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/rails-dev/attachments/20250115/2085dc7c/attachment-0001.htm>