Thanks for the PR, @JoshuaKGoldberg!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	c80d100
🔍 Latest deploy log	https://app.netlify.com/projects/typescript-eslint/deploys/68dacf387a00670008e5b024
😎 Deploy Preview	https://deploy-preview-11663--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 97 (🟢 up 14 from production) Accessibility: 97 (no change from production) Best Practices: 100 (no change from production) SEO: 92 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

View your CI Pipeline Execution ↗ for commit c80d100

☁️ Nx Cloud last updated this comment at 2025-09-29 18:42:18 UTC

This is a breaking change, no? RuleModule is a public type, so code written against v8.45.0 such as:

import { TSESLint, TSESTree } from '@typescript-eslint/utils'
const rule: TSESLint.RuleModule<'foo', []> = {
  name: 'my-rule',
  ...
}

Now fails to typecheck with v8.46.0+.

It was added in one version and immediately removed in the next version because it introduced bugs. From our POV that is NOT a breaking change - it should not have landed at all.

@jfirebaugh FWIW we were intending to do an immediate patch release to revert it, but ran into CI/automation issues, so it ended up just going out as part of the next regularly-scheduled minor, rather than its own patch.

I see... I guess we upgraded at exactly the wrong time, such that we had to add name properties to keep things building with 8.45.0 and then remove them again with 8.46.0.