feat(linter): update allowed ESLint config file extensions #30127
+12
−3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
TorinFrancis
force-pushed
the
eslint/typescript-config-support
branch
2 times, most recently
from
196a78d to
6285a20
Compare
TorinFrancis
force-pushed
the
eslint/typescript-config-support
branch
from
6285a20 to
2e4b2a2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ESLint added experimental support for typescript config files since 9.9.0, and as of 9.18.0 that support is stable. This PR add ts/mts/cts to the list of known eslint config files, and adds the same extensions to config file generators
Current Behavior
Expected Behavior
Related Issue(s)
No issues, but addresses this discussion