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	b483190
🔍 Latest deploy log	https://app.netlify.com/projects/typescript-eslint/deploys/6909f96ce4a3fa0008cc3099
😎 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: 91 (🔴 down 5 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 commitb483190

☁️Nx Cloud last updated this comment at2025-11-04 13:14:21 UTC

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

Can't reproduce test errors in local development.
In test,parseSettings.singleRun frompackages/typescript-estree/src/parser.ts/parseAndGenerateServices isfalse.
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 affectssingleRun.

@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 whetherCI=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 nxtest 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.66%. Comparing base (5ec8c58) to head (b483190).
⚠️ Report is 199 commits behind head on main.

@@            Coverage Diff             @@##             main   #11327      +/-   ##==========================================- Coverage   90.86%   90.66%   -0.20%==========================================  Files         503      518      +15       Lines       51028    52435    +1407       Branches     8418     8686     +268     ==========================================+ Hits        46366    47541    +1175- Misses       4648     4880     +232  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 whenextraFileExtensions is set &projectService is truthy. But, I don't know how to write test scenarios and where to test them.

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

WhensingleRun &projectService is true and givenextraFileExtensions inpackages/typescript-estree/tests/lib/semanticInfo-singleRun.test.ts, check the program is generated.

constresultProgram=parseAndGenerateServices(code,options).services.program;expect(resultProgram).toStrictEqual(mockProgram);

Because, the code is to solve the bug that occurs when programInstance is not found in the singleRun environment.