Skip to content

Conversation

@ROpdebee
Copy link
Owner

We're using some ES2022 features, so let's make sure we compile to browsers that support those features, thus maybe transpiling less. Let's also configure TypeScript to use typings limited to those browsers, otherwise it might allow us to use things like Iterator#map, which are barely available in current browsers. That'll also avoid the Array#at situation from a
few years back.

Speaking of Array#at, seeing as all major browsers have supported it for several years now, let's start embracing it too.

We're using some ES2022 features, so let's make sure we compile
to browsers that support those features, thus maybe transpiling
less. Let's also configure TypeScript to use typings limited to
those browsers, otherwise it might allow us to use things like
`Iterator#map`, which are barely available in current browsers.
That'll also avoid the `Array#at` situation from a few years
back.
@ROpdebee ROpdebee added the build label May 14, 2025
We avoided this in the past due to it being too new, but by now
it's been adopted in major browsers for several years already.
@ROpdebee ROpdebee force-pushed the upgrade-browsers branch from 57df039 to ba32735 Compare May 14, 2025 12:25
@ROpdebee ROpdebee marked this pull request as draft May 14, 2025 12:25
@ROpdebee
Copy link
Owner Author

ROpdebee commented May 14, 2025

nativejsx is throwing another spanner in the works. It depends on escodegen to output the transformed code back into a string, but escodegen hasn't been maintained in a while and doesn't support newer JS syntax, which is causing compilation to fail.

I think it's time to switch away from nativejsx. That needs to happen before this PR can pass.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants