parse5 VS PEG.js

A relatively stable option would probably be to just use puppeteer directly to spawn a headless chrome, and extract the html that way. If you want to parse the html, I recommend feeding that into parse5.

After some googling, I landed on parse5 which appeared to have wide usage and offered a simple, low-level tree API at its core.

We do not use existing open-source solutions such as parse5 for two reasons:

Here's a javascript library that lets you generate your own language that compiles to Javascript. https://pegjs.org/ It's a compiler generator. You can either use the command line tool and feed it your grammar (You have to write that) and use the generated parser.js which can then run your program, or use peg.js as a dependency and generate your parser at run time before feeding it your program.

The library they're having trouble with is the most common parser generator in javascript, peg.js, which has about 80% of the market

Currently, I have only POC the grammar and language and parser are created using https://pegjs.org/

In past blog posts, where I've written about PEG, I've used Parsimonious in Python, such as three of my solutions to the 2020 Advent Of Code challenges (here, (here)[https://dev.to/meseta/advent-of-code-day-18-finally-using-peg-grammar-in-python-in-the-way-it-s-supposed-to-3253], and (here)[https://dev.to/meseta/advent-of-code-day-19-abusing-peg-grammar-in-python-the-way-it-s-not-supposed-to-2beg]). This time, because the rest of the website is javascript, I will be using PEG.js instead to avoid adding an extra programming language to the codebase.

Update: I started writing a grammar for this language in PEG using PEG.js. This was super fun, I'll take a stab at an interpreter next, that should be much harder.

I was going to post the same thing. This really helped me understand the concepts better back in the day. They also have examples for some popular languages on their github: https://github.com/pegjs/pegjs/tree/master/examples