Felix Boehm

I was thinking of tokenizer modes – sorry about the confusion. I'm not sure how useful exporting insertion modes would be, as the parser is pretty hard to extend in...

I'm up for having this. Imho it should be a separate module outside of the core parse5 package. I am still split on whether it should be a part of...

Sounds good 👌 You should be able to create a new repositories in the @parse5 org – lmk if you encounter any issues.

I think we can close this with the https://github.com/parse5/parse5-tools repo :)

From my understanding, the `overrides` section _extends_ the base lints. This is also supported by the test failure in #411, which reported several issues found with the latest version of...

> `ts` files didn't have the unicorn rules or the recommended rules because of that I am a bit confused as to why we saw errors in https://github.com/inikulin/parse5/runs/5282607937 👀

I just tried replicating this locally, and adding `eslint:recommended` to the override doesn't change anything for me. The override extends the `prettier` preset and therefore disables the `curly` rule that...

> so im pretty confused as to why curly gets enabled here. `curly` is [disabled in `eslint-config-prettier`](https://github.com/prettier/eslint-config-prettier/blob/7c0eea65da47e24e101930b37ac3b36f10ccb54f/index.js#L10), which is part of the override.

This is not something that's particularly easy to do with the rewriting stream. One approach would be: ```js // Remove all `article` tags and their contents let articleCount = 0;...

The big issue here is the parser, which uses a lot of *internal* methods, which are used by functions called by the parser (eg. `startTagInCell`). I am unsure of the...