Bryan Mishkin

@mdjermanovic thanks for the context, that's helpful. It sounds like there is support for my original proposal (i.e. warning on unused directives). But I haven't yet heard opinions on the...

@ljharb that's a great argument for erroring by default, which I support. I think the main question is just whether we're okay with the potential semver implications of erroring by...

@nzakas your questions have got me thinking that the current boolean design of these options is particularly confusing and unintuitive, making it hard to predict the interplay. What if I...

Targeting v9 should give us ample time (I assume a year) to communicate about this upcoming breaking change and help rules prepare for it. Other ways we could help rules...

With some effort, we/I could write a script to download the ~3,500 eslint plugins ([titled eslint-plugin-*](https://www.npmjs.com/search?q=eslint-plugin-*&ranking=popularity&page=1&perPage=20) or [keyword:eslint-plugin,eslintplugin](https://www.npmjs.com/search?q=keywords%3Aeslint-plugin%2Ceslintplugin)) from NPM or github (hopefully without hitting rate-limiting), then check files in...

I put together a repository called [eslint-ecosystem-analyzer](https://github.com/bmish/eslint-ecosystem-analyzer) with scripts to perform an analysis of the ESLint plugin ecosystem. It retrieves the top ESLint plugin repositories by searching GitHub and then...

Thanks for the feedback! I'll work on a single RFC in the near future.

I still plan to work on this hopefully in the near future so we can target ESLint v9.

I have opened up an RFC for this: * https://github.com/eslint/rfcs/pull/85

@nzakas good point, I updated the description to include a more detailed table of the return types.