You won't find it in any of the academic literature because it's not an academic project: <a href="https://bablr.org/" rel="nofollow">https://bablr.org/</a><p>BABLR is just the extensible streaming parser framework, but it has a few key things going for it:
1. Gap support like Hazel has, but for any language it can parse
2. Streaming parse results, which make multi-pass stream transformation easy
3. The ability to consolidate and take over the work currently done by Treesitter, LSP, Git, and the IDE itself.
So bablr is from you?<p>"BABLR is a parser framework roughly comparable to Tree-sitter, but built from the ground up for the web"<p>I have to admit, I don't know why I would stop using my wasm build of treesitter that works amazing on the web for something that is "conditionally production ready". Also I don't see where your project mixed visual and textual code like this paper here explores?