Skip to content

Fix ESLint build failure by removing invalid @typescript-eslint direc…#30

Merged
danribes merged 1 commit into
mainfrom
claude/investigate-merge-deployment-01Q2461BUQ7ZSsYshZYL8VF7
Dec 11, 2025
Merged

Fix ESLint build failure by removing invalid @typescript-eslint direc…#30
danribes merged 1 commit into
mainfrom
claude/investigate-merge-deployment-01Q2461BUQ7ZSsYshZYL8VF7

Conversation

@danribes

Copy link
Copy Markdown
Owner

…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.

…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.
@danribes danribes merged commit 1374ecc into main Dec 11, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants