Christian Clason

> Since the main branch has already broken user configurations, it wouldn't be a particularly big issue if it continues to break user queries, lol. Well, that's not the right...

> But if we are certain about making this change, we could first remove #make-range in the master branch. This will likely only require changes to the query, because after...

Looks good to me; if this is incorrect, it should fail pretty badly (easy to manually test with one of the quantified captures here). @ribru17 ?

@TravonteD

Ideally, a snapshot of the repo with all generated files (that are omitted in the repo) included, plus a wasm artifact. Semver is also expected (patch for fixes that don't...

(And WASM parsers as first-tier targets means that not all stdlib functions can be used in scanners -- this is why building the parser now fails on macOS and friends:...

Yes. Upstream is working on it.

Not that I know of (and, sorry to say, I personally don't care about package repositories, so I'm not really able to help here).

This means that the original issue is too old and outdated, and we need a new issue that clearly (and reproducibly!) demonstrates the exact _current_ problems, with exact steps starting...

First thing is always to check if the parser exposes enough information to capture such constructs. (You can check with `:InspectTree`.) If not, you'll need to raise this with tree-sitter-javascript.