Thanks for the PR,@auvred!

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 onhttps://opencollective.com/typescript-eslint.

✅ Deploy Preview fortypescript-eslint ready!

Name	Link
🔨 Latest commit	8b6c1ce
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/65a7b2d9ac170a0008e800e7
😎 Deploy Preview	https://deploy-preview-8265--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 94 (🔴 down 3 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (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 yourNetlify site configuration.

I don't have experience with the scope analyzer, but if the tests are passing it LGTM.

It looks like this introduced a regression intoconsistent-type-imports.

importtypeFoofrom'foo';// Type import "Foo" is used by decorator metadataexport={}asFoo;

filed#8330