Fix ESLint build failure by removing invalid @typescript-eslint direc…#30
Merged
danribes merged 1 commit intoDec 11, 2025
Conversation
…tive The build was failing because sitemap.test.ts had eslint-disable-next-line comments for @typescript-eslint/no-explicit-any, but the @typescript-eslint plugin is not configured in .eslintrc.json. ESLint throws an error when encountering disable comments for undefined rules. Fixed by removing the unnecessary disable comments and replacing the `any` type with a more specific `Record<string, string>` type.
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
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.
…tive
The build was failing because sitemap.test.ts had eslint-disable-next-line comments for @typescript-eslint/no-explicit-any, but the @typescript-eslint plugin is not configured in .eslintrc.json. ESLint throws an error when encountering disable comments for undefined rules.
Fixed by removing the unnecessary disable comments and replacing the
anytype with a more specificRecord<string, string>type.