Bryan Mishkin

Which documentation is missing? In [eslint-plugin-vitest](https://github.com/vitest-dev/eslint-plugin-vitest), I see that a generated rules list is present in the README, and the rule docs have generated headers. However, when I run eslint-doc-generator...

I did some investigation. eslint-plugin-vitest exports a `configs` object: ```json { "legacy-recommended": { "plugins": [ "@vitest" ], "rules": { "@vitest/expect-expect": "error", "@vitest/no-identical-title": "error", "...": "..." } }, "legacy-all": { "plugins":...

We shouldn't need a new option to fix this bug in eslint-doc-generator. It should be possible to fix eslint-doc-generator so that it automatically works for any eslint plugin regardless of...

In your plugin, shouldn't it always be: ```md # Enforce having expectation in test body (vitest/expect-expect) ``` I don't think the user can refer to the rule with `@vitest/`. You...

I would like to make sure we work with ESLint v9. However, I'm not actually sure of any ESLint v9 specific issues. The peer dependency issue in #525 is not...

I haven't really identified a specific blocker with flat configs. That issue was more intended to investigate whether flat configs will need additional work to support. As long as flat...

@MikeMcC399 yes I am open to contributions so please continue filing issues/PRs with any suggestions. I am busy traveling recently but would like to get things updated/modernized in this repository...

@MikeMcC399 really appreciate all the issues and PRs you filed. I believe I have addressed everything related to updating the dev environment (Node, ESLint, TypeScript, and all other dependencies) for...

That sounds fine to me.

Nice, yes I'd be interested in moving to both ESM and TypeScript (separately is fine). Would there be any user-facing impact from the ESM conversion?