chore: remove unused tsconfig.eslint.json#6524
Merged
mcollina merged 1 commit intofastify:mainfrom Feb 22, 2026
Merged
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It seems like
./types/tsconfig.eslint.jsoncan be removed, because it is not used after migration toneosstandardin #5509.Before migration, this TSConfig was referenced from
./types/.eslintrc.json. But that file is removed in the above-mentioned PR. Seems likeneosstandarddoes not need it. @voxpelli, is that correct?The file in question does not cause any harm. At first, I only wanted to remove
../test/typesfrom theincludes, which looks strange. Perhaps it is worth removing it all, since ESLint does not need it anyways.Checklist
npm run test && npm run benchmark --if-presentand the Code of conduct