Thanks for the PR,@nayounsang!

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	1282ebc
🔍 Latest deploy log	https://app.netlify.com/projects/typescript-eslint/deploys/6910a5779626700008eb8d0f
😎 Deploy Preview	https://deploy-preview-11747--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 90 (🔴 down 6 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 yourNetlify project configuration.

View yourCI Pipeline Execution ↗ for commit1282ebc

☁️Nx Cloud last updated this comment at2025-11-09 14:43:05 UTC

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.67%. Comparing base (189a7f7) to head (1282ebc).

@@           Coverage Diff           @@##             main   #11747   +/-   ##=======================================  Coverage   90.66%   90.67%           =======================================  Files         518      518             Lines       52444    52447    +3       Branches     8690     8691    +1     =======================================+ Hits        47548    47554    +6+ Misses       4882     4879    -3  Partials       14       14

But also the docs to have an (IMO) clear and explicit example of how to call it:
https://typescript-eslint.io/packages/scope-manager#analyzetree-options
I.e. You haven't parsed with ranges either and that'll potentially cause a crash later too.

range doesn't related to the issue.
range is used bypackages/scope-manager/src/scope/FunctionScope.ts.
This may lead to incorrect comparisons, but I think it should be addressed as a different issue anyway.

constbodyStart=this.block.body?.range[0]??-1;

// It's invalid resolution in the following case:return!((variable.scope===this&&ref.identifier.range[0]<bodyStart&&// the reference is in the parameter part.variable.defs.every(d=>d.name.range[0]>=bodyStart))// the variable is in the body.);