fix: dependency updates in preparation for adding typescript

[wayfarer3130]

Just some changes for v2 to start updating versions/packaging for changes to typescript.

[pimterry]

Browser tests were failing (here and in the other PR) due to GitHub changing ubuntu-latest to Ubuntu-24.04, which apparently requires some different setup for Chrome, and broke the browser tests. I've pinned that bit of the job to 22.04 for now, which should resolve this for now (for a couple of years at least) and so the v2 branch now passes correctly. If you rebase onto the latest v2 branch that will resolve that issue.

Looks like something else in this PR is breaking the other jobs though, so that will need investigation.

I see you've pulled out the dropping-dist change into this PR. I could be persuaded either way on this, let's see what @Mr0grog thinks, I'm happy to go with whatever you two agree on.

[Mr0grog]

Looks like something else in this PR is breaking the other jobs though, so that will need investigation.

Ahhh, yeah, back in #190, #191, and #195, there were some reasonably complex interdependencies between a lot of the dev dependencies. You can’t just update them all to latest; they do not all work together in all versions or all supported Node.js versions. This might be a bit complex to unravel.

I’m almost certain some of these upgrades will also require removing some Node.js versions from the test matrix. They just aren’t compatible with Node.js versions as old as we currently run tests in.

(Back when I was making those dev updates, I did not upgrade everything to the latest possible because I was trying to keep the divergence between dev and runtime Node.js support as small as possible. We eventually agreed they don’t have to stay perfectly aligned, and that skew will just have to become larger with a lot the changes we’re talking about for 2.0. But it will always present complexities, I think, since the compatibility goals of this library, even in 2.0, are just way wider than what most of the JS community is targeting these days.)

I see you've pulled out the dropping-dist change into this PR. I could be persuaded either way on this, let's see what @Mr0grog thinks, I'm happy to go with whatever you two agree on.

I am somewhat ambivalent here. I think it’s nice that previous versions have been easily downloadable directly from raw.github.com, and that will end with this change. But there are other ways — it could be included as an asset on releases in GitHub. I think this is fine as long as we are planning something like that. This should at least remove discussion of downloading from dist in the README, though.