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.

☁️ Nx Cloud Report

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

📂 See all runs for this branch

Sent with 💌 fromNxCloud.

Codecov Report

Merging#6426 (3a8b206) intov6 (c036fe3) willdecrease coverage by0.09%.
The diff coverage is0.00%.

@@            Coverage Diff             @@##               v6    #6426      +/-   ##==========================================- Coverage   87.46%   87.38%   -0.09%==========================================  Files         374      374                Lines       12879    12891      +12       Branches     3811     3813       +2     ==========================================  Hits        11265    11265- Misses       1229     1241      +12  Partials      385      385

hyperfine measurements are not very promising:

What's the command you used to grab the hyperfine measurement?
I've been raw-dogging the entire codebase lint run via./node_modules/.bin/eslint . (to work around yarn and ensure i run eslint directly).

Do we have a bigger type-aware codebase we can test on?
Maybe we can just turn on every single rule in our codebase for the test run to increase the possibility of cache hits (I know we're fairly conservative in our type-aware linting ATM).

yarn lint --skip-nx-cache - it's deep in the edit history. I do want to do more thorough checking, including on the codebase as a whole. And there might be more type checker APIs that should be cached. I like the turning on every rule, good idea!

✅ Deploy Preview fortypescript-eslint ready!

Name	Link
🔨 Latest commit	3a8b206
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/642db4d6f2fa4100085a20b0
😎 Deploy Preview	https://deploy-preview-6426--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to yourNetlify site settings.

☁️ Nx Cloud Report

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

📂 See all runs for this branch

Sent with 💌 fromNxCloud.

@bradzacher not-very-promising news on this:

• Runningtime MEMOIZE_TYPE_CHECKING_APIS=true yarn lint --skip-nx-cache takes ~60 seconds for me - same astime yarn lint
• Runningtime MEMOIZE_TYPE_CHECKING_APIS=true yarn lint-many runs out of memory (instead of taking ~110 seconds)

I think it'd make sense to ship this change, since it's small and additive and labeled asEXPERIMENTAL_. Thoughts?

This was unintentionally auto-closed when we merged thev6 branch 🙃 it'll be recreated.

I'm more hopeful about theEXPERIMENTAL_useProjectService parser option (#6754). Closing this for now.

If someone does think this PR would benefit them, feel free to post an explanation why! We can always re-open - or even better,you the reader can open it and take ownership.