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

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	a2e2d21
🔍 Latest deploy log	https://app.netlify.com/projects/typescript-eslint/deploys/68569243208bed0007f8f850
😎 Deploy Preview	https://deploy-preview-11327--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 (🟢 up 1 from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (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 a2e2d21.

☁️ Nx Cloud last updated this comment at 2025-06-21 11:10:38 UTC

Why tests was failed in CI?
In my local, there was no problem.

Can't reproduce test errors in local development.
In test, parseSettings.singleRun from packages/typescript-estree/src/parser.ts/parseAndGenerateServices is false.
So, it doesn't seem to be related to this commit.
I verified that the test results and (of course) the singleRun results did not change before and after the commit.
This work only affects singleRun.