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	ca1e819
🔍 Latest deploy log	https://app.netlify.com/projects/typescript-eslint/deploys/687baed9ff3160000827c560
😎 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: 96 (🟢 up 2 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 ca1e819

☁️ Nx Cloud last updated this comment at 2025-07-19 14:48:05 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.

@JoshuaKGoldberg @nayounsang Ok this one drove me a little insane working my way to a reproduction, but it actually has nothing to do with caching, it is all to do with whether CI=true is set or not (which is why it happens only on CI and not locally by default).

In other words, you should be able to repro with:

CI=true TYPESCRIPT_ESLINT_PROJECT_SERVICE=true nx test typescript-estree --skip-nx-cache

Thanks for helping us find the cause of this weird bug. Now let's fix our logic to fix the CI test failure.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.86%. Comparing base (5ec8c58) to head (ca1e819).

@@           Coverage Diff           @@
##             main   #11327   +/-   ##
=======================================
  Coverage   90.86%   90.86%           
=======================================
  Files         503      503           
  Lines       51028    51028           
  Branches     8418     8418           
=======================================
  Hits        46366    46366           
  Misses       4648     4648           
  Partials       14       14           

Hi @JoshuaKGoldberg . Thank you for always helping me. I would like to ask you a question.
I want to test that singleRun works without any problems even when extraFileExtensions is set when projectService is truthy. But, I don't know how to write test scenarios and where to test them.

(I can see the processing extraFileExtensions logic in packages/typescript-estree/src/useProgramFromProjectService.ts
, but... I don't know if it's related to this issue.)