nearley
Chevrotain
Our great sponsors
| nearley | Chevrotain | |
|---|---|---|
| 3 | 3 | |
| 3,545 | 2,392 | |
| - | 1.3% | |
| 0.0 | 7.2 | |
| 8 months ago | 3 days ago | |
| JavaScript | TypeScript | |
| MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nearley
-
Writing a C compiler in 500 lines of Python
While I suspect I would learn more writing a tokenizer and parsing logic myself I find grammars much easier to read and maintain.
ANTLR is pretty good and is supported across several languages and something I had previously used for some quick Elasticsearch query syntax munging in Python. It also means you can often start from an already existing grammar.
The JS version of ANTLR didn't seem to work for me so for the SQL/JSONPath stuff ended up using the Moo lever and Nearly parser which was rather pleasant. https://nearley.js.org
- Parser generators vs. handwritten parsers: surveying major languages in 2021
-
Applicative Parsing
Parsers in nearley.js [1] are written in a very readable EBNF-like DSL; then they get desugared down to a JS file that's a lot like your snippet.
Chevrotain
-
Ohm: A library and language for building parsers, interpreters, compilers, etc.
How does this compare with Chevrotain[1]?
More specifically, can I build lexers with Ohm? Can it generate a syntax diagram from a grammar?
-
Introduction to Lexers, Parsers and Interpreters with Chevrotain
To learn more about Chevrotain visit: https://chevrotain.io/
-
Why are you building a programming language?
I don't think I'll have time to make one any time soon, unfortunately. My original plan was to write a compiler in TypeScript using Chevrotain, and see if it's possible to compile down to TypeScript's AST and feed that into its own compiler programmatically. Basically piggybacking on Microsoft's hard work (work smart, not hard). I don't know if it's possible, but it's what I'd try first.
What are some alternatives?
PEG.js - PEG.js: Parser generator for JavaScript
Jison - Bison in JavaScript.
markdown-it - Markdown parser, done right. 100% CommonMark support, extensions, syntax plugins & high speed
xml2js - XML to JavaScript object converter.
parsec 🌌 - 🌌 Tiniest body parser in the universe. Built for modern Node.js
parse5 - HTML parsing/serialization toolset for Node.js. WHATWG HTML Living Standard (aka HTML5)-compliant.
csv-parser - Streaming csv parser inspired by binary-csv that aims to be faster than everyone else
neat-csv - Fast CSV parser
URI.js - Javascript URL mutation library