Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
feat: deprecate tseslint.config()#11531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
feat: deprecate tseslint.config()#11531
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Thanks for the PR,@kirkwaiblinger! 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. |
netlifybot commentedAug 26, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
✅ Deploy Preview fortypescript-eslint ready!
To edit notification comments on pull requests, go to yourNetlify project configuration. |
nx-cloudbot commentedAug 26, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
View yourCI Pipeline Execution ↗ for commit1576c1f
☁️Nx Cloud last updated this comment at |
Uh oh!
There was an error while loading.Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Always nice to see a formatter issue filed as a result of docs work 😅
Great stuff!
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Josh Goldberg ✨ <git@joshuakgoldberg.com>
Co-authored-by: Josh Goldberg ✨ <git@joshuakgoldberg.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
LGTM
d7614a7
intotypescript-eslint:mainUh oh!
There was an error while loading.Please reload this page.
stefanprobst commentedSep 2, 2025 • edited
Loading Uh oh!
There was an error while loading.Please reload this page.
edited
Uh oh!
There was an error while loading.Please reload this page.
is the |
corneliusroemer commentedSep 4, 2025
Migration guide for deprecated |
This isn't directly related to this PR, and we anyways try to avoid commenting on closed PRs (docs). Would you mind reaching out to us with one of the methods in the contributing guide to continue the conversation? Thanks! |
Uh oh!
There was an error while loading.Please reload this page.
Important
If you've come across this PR looking for info on migrating off of
tseslint.config()
, please seehttps://typescript-eslint.io/packages/typescript-eslint#migrating-to-defineconfigPR Checklist
Overview
tseslint.config()
in the docs everywhere withdefineConfig()
/** @deprecated */
totseslint.config()
.defineConfig()
Questions
defineConfig(a, b, c)
ordefineConfig([a, b, c])
style? The eslint docs (inexplicably) usedefineConfig([a, b, c])
throughout, butdefineConfig(a, b, c)
is much better in a TS context since each argument's type is checked individually. I've gone with that approach for now, but we can change to match their style if we want.