Bryan Mishkin

Not sure why CI is failing. Ran tests locally under Node 19 and didn't see an issue.

I can reproduce it locally with `npm test --runInBand` under Node 19. But there are no hints about what's causing the failed exit code. Might be related: https://github.com/facebook/jest/issues/9324. Sounds likely...

Cool, I would definitely like to support TypeScript configs.

Thanks for the issue. I'd be interested to see a before/after example where centering looks notably better. Also, even if it looks better for one row, it might not look...

@MichaelDeBoey would this qualify for @eslint-community as a backup? > My preference would be to partner up with a group or company that is active in the React Native scene....

Sounds like a good idea. Perhaps a name like `no-matching-violation-suggest-message-ids`.

I like this idea. I've always wanted to make schemas more helpful. Maybe a dedicated rule for it called `require-meta-schema-description` (as it goes beyond [require-meta-schema](https://github.com/eslint-community/eslint-plugin-eslint-plugin/blob/main/docs/rules/require-meta-schema.md)). Could use these descriptions in...

Per https://github.com/eslint/eslint/issues/18095#issuecomment-1951414598, ideally plugins would continue to use the exported `configs` object to contain all their configs, both legacy and flat (temporarily using `flat/` prefixes for flat configs before moving...

Yes, I think we would need separate templates for each type of plugin we can generate: - `plugin` (existing, CJS) - `plugin-esm` - `plugin-ts` - `rule` (existing, CJS) - `rule-esm`...

@JoshuaKGoldberg @bradzacher is there a standard template for new TypeScript plugins/rules anywhere or could we put one together to use in this generator?