Big Internal Change Idea

Currently, parsers are constructed like this: Parser((context) => { ... }) and they simply access the other parsers via the scope of the lambda.

The idea is to provide more info to the parser instance for analysis (e.g. finding infinite loops).

const p = new Parser({
    type: SOME_ENUM.VALUE,
    advancing?: ADVANCING | UNKNOWN | NOT_ADVANCING,
    deps: [Parser1, Parser2].
});

p.func = function some_name(context) => {
    const parser1 = p.getDep(0); // this has the correct type (Parser1)
}

This allows for a validation function on the parser that checks for infinite loops.
This also enables building a string representation of the parser structure.

The issue names no files or tests; start by locating the current Parser constructor and the lambda-based dependency access. Read how parser instances are represented and how their functions are assigned. Done would require an agreed parser metadata and dependency design, validation for infinite loops, and a string representation of parser structure.