Skip to content

Commit 3719195

Browse files
nchalla3claude
andcommitted
add ESLint config and install missing lint dependencies
next lint was failing in CI because no ESLint config existed, causing it to prompt interactively and exit with code 1. Adds eslint.config.mjs with next/core-web-vitals + next/typescript rules. Pre-existing style violations (unescaped entities, explicit any, a-vs-Link) are downgraded to warnings so CI gates on new errors without blocking on legacy code. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 7bfa4fd commit 3719195

3 files changed

Lines changed: 5237 additions & 1214 deletions

File tree

eslint.config.mjs

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
import { dirname } from "path";
2+
import { fileURLToPath } from "url";
3+
import { FlatCompat } from "@eslint/eslintrc";
4+
5+
const __filename = fileURLToPath(import.meta.url);
6+
const __dirname = dirname(__filename);
7+
8+
const compat = new FlatCompat({
9+
baseDirectory: __dirname,
10+
});
11+
12+
const eslintConfig = [
13+
...compat.extends("next/core-web-vitals", "next/typescript"),
14+
{
15+
// Downgrade pre-existing style violations to warnings so CI doesn't block
16+
// on legacy code. These are not runtime bugs — the site functions correctly
17+
// with them present. Tighten these back to "error" once the backlog is cleared.
18+
rules: {
19+
"react/no-unescaped-entities": "warn",
20+
"@typescript-eslint/no-explicit-any": "warn",
21+
"@next/next/no-html-link-for-pages": "warn",
22+
},
23+
},
24+
];
25+
26+
export default eslintConfig;

0 commit comments

Comments
 (0)