fix(eslint-plugin): remove duplicate import RuleModuleWithMetaDocs

[abrahamguo]

PR Checklist

• Addresses an existing open issue: fixes #000
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

In #9339, @JoshuaKGoldberg introduced a regression causing a duplicate import identifier. In a project that consumes @typescript-eslint/[email protected], this causes two TypeScript errors in that file (if skipLibCheck is false), complaining about the duplicate import.

I'm not sure, by the way, why this is not a TS error in the repo itself, but causes a TS error when in the node_modules of another package.
Should we consider turning on skipLibCheck in this repo?
Also, I did a cursory search and was unable to find any rule in eslint, typescript-eslint or eslint-plugin-import that would allow us to catch issues like these 🙁

[typescript-eslint]

Thanks for the PR, @abrahamguo!

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.

[netlify]

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	ae2bb65
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/6682a0f9b0454e00085328d8
😎 Deploy Preview	https://deploy-preview-9465--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 (🔴 down 3 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 90 (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 site configuration.

[JoshuaKGoldberg]

Oops. Thanks for the catch!

[JoshuaKGoldberg]

Should we consider turning on skipLibCheck in this repo?

...on or off?

I would be +1 on a followup issue around some kind of end-to-end / integration test to catch these errors, for sure. Good call!

[abrahamguo]

oh yes haha, I did mean "turn skipLibCheck off".

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit ae2bb65. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 32 targets

• nx test eslint-plugin --coverage=false
• nx test typescript-estree --coverage=false
• nx test eslint-plugin
• nx run types:build
• nx test visitor-keys --coverage=false
• nx test typescript-eslint --coverage=false
• nx run repo-tools:postinstall-script
• nx test rule-schema-to-typescript-types --coverage=false
• nx test type-utils --coverage=false
• nx test utils --coverage=false
• nx test parser --coverage=false
• nx test scope-manager --coverage=false
• nx test repo-tools --coverage=false
• nx run-many --target=test --parallel --exclude integration-tests --exclude website --exclude website-eslint
• nx test typescript-estree
• nx test type-utils
• nx test visitor-keys
• nx test utils
• nx test typescript-eslint
• nx test scope-manager
• nx test rule-schema-to-typescript-types
• nx test repo-tools
• nx test parser
• nx test eslint-plugin-internal
• nx test eslint-plugin-internal --coverage=false
• nx run-many --target=build --parallel --exclude=website --exclude=website-eslint
• nx test ast-spec --coverage=false
• nx test ast-spec
• nx run-many --target=lint --parallel --exclude eslint-plugin
• nx run-many --target=typecheck --parallel
• nx run integration-tests:test
• nx run repo-tools:generate-configs

---

Sent with 💌 from NxCloud.