V7 Planned Changes

[aladdin-add]

Starting a list of my desired breaking changes, feedback welcome. We can perform this release once we have compiled enough changes.

Planned:

• Enable additional recommended rules:
  • Add new rule require-meta-default-options #502
  • Add new rule no-meta-schema-default #503
  • Add new rule require-meta-schema-description #490
  • feat: Add new rule no-meta-replaced-by #518
  • Note: the new rule require-meta-docs-recommended is NOT intended to become a recommended rule, so we won't add this
• Change rule options
  • TODO
• Supported Node.js versions
  • Drop Node besides 20, 22, 24: https://github.com/nodejs/Release
• Supported ESLint versions
  • >8.57.1 or just >9.0.0
• Migrations
  • feat: move to ESM only #516 (more info: ESM)
  • Add TypeScript type-checking to all rules #310

For reference, V6 was released 2024-04-10 (CHANGELOG, discussion in #269).

[azat-io]

+1 for TS config support 👍

[43081j]

Convert package to ESM or TypeScript

yes please

we're currently in the process of moving quite a few eslint plugins to esm-only, so let me know if you want any help

[drake-nathan]

TS or not, it should ship with types. If you're making a breaking change anyways, I would personally ship it in TS, ESM only, and ESLint >=9.

I'm happy to help with this effort!

[michaelfaith]

Need any help with this work?

[43081j]

here's the ESM conversion if its of any use:
main...43081j:eslint-plugin-eslint-plugin:esm-only

happy to open it as a PR if its a direction we want to go in

[bmish]

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?

[43081j]

It should only affect people who use commonjs and node <20. But they can just migrate to eslint.config.mjs without having to migrate their entire project, or they can use newer node.

Other than that, everything should be pretty much the same

[michaelfaith]

If #516 lands, i'd be happy to help with the migration to TypeScript, if needed.