Fix VS Code LSP crash

[flying-sheep]

As mentioned in #434 (comment), getrandom has a workaround built in around the fact that node.js’s ESM story is still not properly solved (rust-random/getrandom#256 (comment))

That workaround exists in getrandom 0.2.8+, but several crates still accepted ahash 0.7.6, which kept the getrandom version at 0.2.7.

This PR bumps the ahash versions we depend on so compatible getrandom versions can be used.

Fixes #434

[flying-sheep]

Please feel free to edit this PR until it fullfills all your quality standards. That’s going to be be faster than having me do it, especially when each edit requires you to manually approve workflow runs.

Alternatively, you can change the workflow approval setting from

Fork pull request workflows from outside collaborators

• Require approval for first-time contributors who are new to GitHub
• Require approval for first-time contributors

to

Fork pull request workflows from outside collaborators

• Require approval for first-time contributors who are new to GitHub
• Require approval for first-time contributors

then I’m happy to work on this until CI passes (unless that would involve releasing a new version of something)

see https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository#controlling-changes-from-forks-to-workflows-in-public-repositories

[tamasfe]

Thanks! I changed the github settings.

[flying-sheep]

Seems like CI passes in any case!

I’m not 100% sure which crates / npm packages need to be compiled and released in which order before the extension can be released with this bugfix, since I used yarn add link:../some/path to use local versions during development. I can only say that before my changes, I could reproduce the issue, and after, I couldn’t anymore. The two necessary changes are

1. the JS workaround in server.js
2. Making sure that the WASM embedded in @taplo/lsp contains getrandom 0.2.8 or later

To add tests for this, you’d need to add VS Code extension tests, which I think is out of scope of this PR.

[ia0]

Thanks!