feat(typescript-estree): skip isTTY version check if user passes loggerFn on unsupported TypeScript version warning

[hyperupcall]

PR Checklist

• Addresses an existing open issue: fixes Skip the isTTY check for printing the "SUPPORTED TYPESCRIPT VERSIONS" message if the user passes in the loggerFn option #3506
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

From the linked PR, this disabled the isTTY heuristic if loggerFn was supplied as an option:

• If loggerFn is a function, then the heuristic is now bypassed completely
• If loggerFn is false, then the heuristic logic runs, but the result is effectively a no-op (nothing is printed in this case)

Additionally, this fixes warn-on-unsupported-ts.test.ts by properly requiring/importing parser.ts for every test. Previously, it would only import once at the start, which prevented the top-level assignment let warnedAboutTSVersion = false (and later assignments/side-effects thereof) from being reset (in warnAboutTSVersion.ts).

It seems TypeScript complains about the await import; the error seems ignored in other places so I ignored it too.

[typescript-eslint]

Thanks for the PR, @hyperupcall!

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.

[netlify]

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	cada6e1
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/65469bbedf4d2e0008c03844
😎 Deploy Preview	https://deploy-preview-7739--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 (🔴 down 2 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (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 site configuration.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit cada6e1. 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

---

✅ Successfully ran 19 targets

• nx test eslint-plugin --coverage=false
• nx test typescript-estree --coverage=false
• nx test scope-manager --coverage=false
• nx run types:build
• nx test type-utils --coverage=false
• nx run repo-tools:postinstall-script
• nx test visitor-keys --coverage=false
• nx test ast-spec --coverage=false
• nx test eslint-plugin-tslint --coverage=false
• nx test utils --coverage=false
• nx test parser --coverage=false
• nx test repo-tools --coverage=false
• nx test rule-schema-to-typescript-types --coverage=false
• nx test eslint-plugin-internal --coverage=false
• nx run-many --target=typecheck --parallel
• nx run-many --target=lint --parallel
• nx run integration-tests:test
• nx run eslint-plugin:generate:configs
• nx run-many --target=build --parallel --exclude=website --exclude=website-eslint

---

Sent with 💌 from NxCloud.

[JoshuaKGoldberg]

💯 great, thanks! Nice to see this 3+ year old issue resolved.

Just a few nitpicks from my end. Because they're not blocking at all I can just touch them up before merging.

[hyperupcall]

Just a few nitpicks from my end. Because they're not blocking at all I can just touch them up before merging.

Sounds good! I'm not sure if my branch is comitable from your end, so feel free to point out the nits, and I'll be able to make the changes if you are not able to.

[JoshuaKGoldberg]

Ah you're right! It's not. If you could make them or grant me access, that'd be great thanks 😄. Otherwise no worries.

[hyperupcall]

If you could make them or grant me access

I wish I had the ability to, but the "maintainers of a repository can edit branches from forks from that repository" feature only works if the fork is owned by a personal account. And this fork is owned by fox-forks, an organization account, not hyperupcall. I even contacted support about it, I'm hoping they add support for that.