Shahar Soel

Perhaps you should try to examine this condition in a more "direct" manner by overloading `consumeInternal` or `consumeToken` and flag every token **index** which has been consumed and then inspect...

I am not sure if web workers are relevant to this issue. Optimization for web-workers may be around reducing initialization time, e.g via serialization, particularly if a new web-worker is...

It seems less likely that separate web workers would be used for the lexer and the parser which would be needed to re-produce this issue. But yeah its the same...

Should possibly be limited to "virtual" Tokens like Indents/outdent So the Lexer will continue handling all the position information.

Hello @Qix- . There is an example for dealing with [Python like indentation here](https://github.com/SAP/chevrotain/blob/master/examples/lexer/python_indentation/python_indentation.js) It is not the prettiest but it works... This issue is more about **cosmetic** API changes...

Separating the bundling and compilations steps was done intentionally. I personally believe it allows greater flexibility dev flows. I see the following issues: ## Issues / Cons ### Major: (not...

My initial impression is is that there are more cons to replacing the `main` / `exports` fields than advantages. And I think it may be best to just implement a...

> The big pro here is that the ES bundle works correctly now: It does export { CstParser, EmbeddedActionsParser, ... } instead of const module = { CstParser, EmbeddedActionsParser };...

Technical discussion on supporting dual style libraries (CJS/ESM). - https://github.com/node-fetch/node-fetch/pull/1227

@NaridaL I appreciate the effort you've put into this PR. 👍 However, it is possible we would be better off by **shelving** it and re-evaluating the status in ~6 months....