Thanks for the PR,@JoshuaKGoldberg!

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	318279b
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/66e59a9bf48f9d0008432618
😎 Deploy Preview	https://deploy-preview-9989--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 4 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 90 (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.

☁️ Nx Cloud Report

CI is running/has finished running commands for commit318279b. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

Sent with 💌 fromNxCloud.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.67%. Comparing base(77e65df) to head(318279b).
Report is 2 commits behind head on main.

@@           Coverage Diff           @@##             main    #9989   +/-   ##=======================================  Coverage   88.67%   88.67%           =======================================  Files         425      425             Lines       14797    14799    +2       Branches     4302     4304    +2     =======================================+ Hits        13121    13123    +2  Misses       1533     1533             Partials      143      143

I have been troubleshooting this issue on my side without realizing there was an open issue/pr to already fix that. I was checking about the fix and wondering about theif inside the try, that involve knowing the subtle difference between theconfig andoptionRawObject, it also feels a bit strange to parse the config file that might not exist and then wait for the exception.

I don't want to overstep, but I have tested the following solution (closer to what was done in 8.4)

if(options.allowDefaultProject?.length){log('Enabling default project: %s',options.defaultProject);letconfigFile:ts.ParsedCommandLine;try{configFile=getParsedConfigFile(tsserver,options.defaultProject,tsconfigRootDir,);}catch(error){thrownewError(`Could not read project service default project '${options.defaultProject}':${(errorasError).message}`,);}service.setCompilerOptionsForInferredProjects(// NOTE: The inferred projects API is not intended for source files when a tsconfig// exists.  There is no API that generates an InferredProjectCompilerOptions suggesting// it is meant for hard coded options passed in. Hard asserting as a work around.// See https://github.com/microsoft/TypeScript/blob/27bcd4cb5a98bce46c9cdd749752703ead021a4b/src/server/protocol.ts#L1904configFile.optionsasts.server.protocol.InferredProjectCompilerOptions,);}

Which will only try to parse the config if we actually want to use a defaultProject.