fix: update getLib for new TypeScript targets ES2021, ES2022

[andersk]

PR Checklist

• Addresses an existing open issue: fixes #000
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

Support for the es2021.full and es2022.full libs was added in #3460 and #4615, but the getLib function wasn’t updated to use them; if target is set to "ES2021" or "ES2022" in tsconfig.json, getLib would incorrectly fall back to ['lib'] rather than ['es2021.full'] or ['es2022.full']. Add these missing cases.

[typescript-eslint]

Thanks for the PR, @andersk!

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	2aeee90
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/6422185fefac7d000775261b
😎 Deploy Preview	https://deploy-preview-6782--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 your Netlify site settings.

[nx-cloud]

☁️ Nx Cloud Report

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

---

✅ Successfully ran 25 targets

• Node 18 - nx test visitor-keys
• Node 18 - nx run-many --target=build --parallel --exclude website
• Node 18 - nx test type-utils
• Node 18 - nx test utils
• Node 14 - nx test scope-manager --coverage=false
• Node 14 - nx run-many --target=build --parallel --exclude website
• Node 18 - nx test scope-manager
• nx run-many --target=typecheck --parallel
• Node 14 - nx test typescript-estree --coverage=false
• Node 18 - nx test eslint-plugin
• Node 14 - nx test type-utils --coverage=false
• Node 14 - nx test eslint-plugin --coverage=false
• Node 18 - nx test parser
• Node 14 - nx test eslint-plugin-tslint --coverage=false
• Node 14 - nx test parser --coverage=false
• Node 18 - nx test eslint-plugin-tslint
• nx run-many --target=lint --parallel
• Node 14 - nx test ast-spec --coverage=false
• Node 14 - nx test visitor-keys --coverage=false
• Node 18 - nx test eslint-plugin-internal
• Node 14 - nx test eslint-plugin-internal --coverage=false
• Node 18 - nx test typescript-estree
• Node 14 - nx test utils --coverage=false
• nx run-many --target=build --parallel --exclude website
• Node 18 - nx test ast-spec

---

Sent with 💌 from NxCloud.

[JoshuaKGoldberg]

Nice find, thanks @andersk!

Out of curiosity - how did you notice this? 😄

[andersk]

I found this in zulip/zulip#24875 where the no-undef rule started complaining about more globals when we switched the TypeScript target from ES2020 to ES2022. (I know you don’t recommend no-undef with typescript-eslint, but we want to prohibit some globals like jQuery that TypeScript thinks are globally available but we want to be explicit about importing.)