This means we can also remove the "update emscripten" xtask, and with it the ureq dependency as requested in #4295.

Ah, I see that you added ureq as a full dependency, so the situation is now worse... Would switching to a different crate as in #4299 work for you? (I'm not happy about the inflated dependency chain in that PR; maybe there is a more light-weight alternative?)

Oh yeah, I hadn't seen that discussion about how ureq is a problem for Microsoft. Thanks for pointing that out @clason; really any HTTP crate would be fine.

Maybe one could simply shell out to curl to grab the package?

On a related note, there's still a huge number of references to emscripten -- in the docs, the xtasks (I guess they can just be removed?), the bindings and the lib. What is the plan there?

Emscripten is still needed for generating the Tree-sitter web binding. It generates the JavaScript->WASM glue that lets us package Tree-sitter as a JavaScript library. What it's not needed for is compiling Tree-sitter parsers to WASM. That can now be done with clang itself, which I think is nice. In particular, now that the native Tree-sitter library can consume WASM binaries, a lot of users might want to use that feature without needing to deal with Emscripten.

That makes sense, thanks for the explanation! (And indeed a very welcome change for us pure-C consumers :))