Parsing in JavaScript: all the tools and libraries you can use(tomassetti.me)
tomassetti.me
Parsing in JavaScript: all the tools and libraries you can use
https://tomassetti.me/parsing-in-javascript/#chevrotain
19 comments
I wrote something similar in JavaScript. You need something like:
function as_and_bs() { return parse_text("aaaaabbbaaaabb", make_grammar( parse_text("root : (\"a\" SEQ \"b\" SEQ)SEQ OPT", iparse_grammar))) }
The code can be found at https://github.com/FransFaase/ParserWorkshop/
function as_and_bs() { return parse_text("aaaaabbbaaaabb", make_grammar( parse_text("root : (\"a\" SEQ \"b\" SEQ)SEQ OPT", iparse_grammar))) }
The code can be found at https://github.com/FransFaase/ParserWorkshop/
I recently used "Arcsecond" JavaScript Parser Combinator library to output some abstract syntax based on John Reynold's "Definitional interpreters for higher-order programming languages".
It's based on Haskell's Parsec parser combinator library, and is zero-dependency.
I was convinced to give it a try based on watching the author's YouTube videos "Parser Combinators From Scratch" on "Low Level JavaScript". Enjoyable series - recommended.
It's based on Haskell's Parsec parser combinator library, and is zero-dependency.
I was convinced to give it a try based on watching the author's YouTube videos "Parser Combinators From Scratch" on "Low Level JavaScript". Enjoyable series - recommended.
hmm this article is a bit outdated; peg.js (mentioned in the article) has been abandoned by the maintainer for a few years now (and it never reached a stable 1.0 ); recently the project was picked up by another team under the name peggy.js https://github.com/peggyjs/peggy
Anyone have experience with Nearley? I recently did some reading on JS parsers and ended up feeling like it was easier to use than most of the others where you have to pay attention to and know some tricks for handling recursive grammar rules. What I don't have a sense for yet is what the downsides of Nearley might be down the road once my grammar gets bigger and/or goes into production, if the performance issues might pop up suddenly and be hard to fix.
I've done a little toy language implementation with Nearley and really enjoyed it. If you have some JS experience under your belt, Nearley should be pretty easy to pick up and I felt it was easy to build on top of the basic building blocks. It's almost too easy to drop into custom JS with Nearley's inline JS syntax, so you can do all sorts of stuff with JS regexes or what not if you can't find a built-in feature that would do what you want.
Unfortunately my project was not big enough that I'd be able to say anything about performace in scale, though. Being JS based has the advantage that you can (depending on your application needs) sometimes move some of that workload to the client :)
Unfortunately my project was not big enough that I'd be able to say anything about performace in scale, though. Being JS based has the advantage that you can (depending on your application needs) sometimes move some of that workload to the client :)
Nearley is amazing. The best implementation of the Earley algorithm I know. It's a great algorithm because you can use any context-free grammar as input and it doesn't require code generation. It's the perfect algorithm for a parse(grammar, input) standard library function.
As far as I know, Nearley implements all optimizations published in the literature. Worst case time complexity is cubic for ambiguous grammars, quadratic for unambiguous grammars and linear for grammars suitable for deterministic algorithms. Performance is still going to be worse than constrained parsers that can handle only a subset of context-free grammars such as deterministic LL(1) parsers. Here's what the Parsing Techniques book says:
> If one has the luxury of being in a position to design the grammar oneself, the choice is simple:
> design the grammar to be LL(1) and use a predictive recursive descent parser.
> This can be summarized as: parsing is a problem only if someone else is in charge of the grammar.
As far as I know, Nearley implements all optimizations published in the literature. Worst case time complexity is cubic for ambiguous grammars, quadratic for unambiguous grammars and linear for grammars suitable for deterministic algorithms. Performance is still going to be worse than constrained parsers that can handle only a subset of context-free grammars such as deterministic LL(1) parsers. Here's what the Parsing Techniques book says:
> If one has the luxury of being in a position to design the grammar oneself, the choice is simple:
> design the grammar to be LL(1) and use a predictive recursive descent parser.
> This can be summarized as: parsing is a problem only if someone else is in charge of the grammar.
This is pretty cool and useful! I had been doing bootleg parser combinators in JavaScript up until now. This works, although being someone who doesn't write Haskell I assume that the magic that makes parser combinators efficient is not easy to implement in most languages. (I've been using nom with Rust on the side too and it seems to do the same naive stuff that I do.)
If you ever want to parse binary data using JavaScript, I will always recommend the excellent Kaitai Struct project.
https://kaitai.io/
If you ever want to parse binary data using JavaScript, I will always recommend the excellent Kaitai Struct project.
https://kaitai.io/
[deleted]
See my library for parsing text: https://github.com/eguneys/tamcher
Earlier this year, I wrote a small interpreting parser in JavaScript, which takes a grammar from a string and parses some input from a string according to the grammar into an AST. It is embedded in the page https://fransfaase.github.io/ParserWorkshop/Online_inter_par...
No Treesitter? I thought it was one of the most performant modern options with an amazing ecosystem around it.
Treesitter is not JS (although the Wasm version can be used from JS). Lezer (https://github.com/lezer-parser/lezer) is similar (it was inspired by Treesitter) and is written in TS.
I'd also suggest using jsfuzz to find sharp corners in your parser. I used it extensively for my recursive-descent BASIC interpreter (along with a test suite) and it found tons of issues.
Another thing that you can use if you're doing JS: any language that compile to JavaScript. Here are a few options:
- Clojure with ClojureScript
- F# with Fable
- Haskell with ghcjs
- OCaml with js_of_ocaml and ReScript
- Racket with RacketScript
- Scala with Scala.js
- Clojure with ClojureScript
- F# with Fable
- Haskell with ghcjs
- OCaml with js_of_ocaml and ReScript
- Racket with RacketScript
- Scala with Scala.js
[deleted]
Although this is an interesting topic to me, I struggle to read the site behind all the cookie warnings and newsletter begging.
[0]: https://github.com/Engelberg/instaparse