Maybe the behavior descripted in [#16232](https://github.com/eslint/eslint/issues/16232#issue-1348130574) is a problem for this parser and not of general eslint.