Shahar Soel

It may be a good idea to "hide" some of the internal properties using symbols instead of string properties.

> My use case is extending my parser to have a OR_LONGEST, which applies all rules, and takes the longest successful match. I don't think this would be possible, Macros...

206K --> 136K (chevrotain.min.js) is good enough for now. Closing this issue.

Fixing this (e.g via state on lexer/parser) is likely to cause too many API changes for too little benefit as I've only encountered an edge case with this state once......

Switching to lodash-es and compiling typescript to ESM instead of commonjs seems to reduce the minified bundle size by ~20% (40Kb).

Done in: https://github.com/Chevrotain/chevrotain/pull/1953 I'm still keeping the UMD artifacts (chevrotain.js / chevrotain.min.js) for browser usage. But from nodejs only ESM is supported.

I suspect that using the [LL(*) plugin](https://github.com/langium/chevrotain-allstar) for chevrotain could get rid of much of the backtracking used in the Java-Parser. @msujew **WDYT?** Example of backtracking production: - https://github.com/jhipster/prettier-java/blob/2f7efa41db2423a200236027afb9f0fe8c198b02/packages/java-parser/src/productions/blocks-and-statements.js#L568-L587 Usage...

Thanks @msujew Do you have any estimate or guess regarding what percentage of these lookaheads can be solved with LL* and what percentage cannot? I am trying to understand if...

Does the xmldom library used in this vscode extension not provide syntax validations? If you have parsing requirements for XML specifically for editor tooling infrastructure This may be of help:...

I have been doing some work on XML Language Services here: - https://github.com/SAP/xml-tools You could use the xml-tools/parser package to get syntax errors. - https://github.com/SAP/xml-tools/tree/master/packages/parser There are additional capabilities in...