@djangocfg/eslint-config 2.1.542 → 2.1.543

package/base.js

@@ -2,11 +2,17 @@ import js from "@eslint/js";
 import eslintConfigPrettier from "eslint-config-prettier";
 import turboPlugin from "eslint-plugin-turbo";
 import tseslint from "typescript-eslint";
-import onlyWarn from "eslint-plugin-only-warn";
 
 /**
  * A shared ESLint configuration for the repository.
  *
+ * `eslint-plugin-only-warn` used to sit at the bottom of this array, rewriting
+ * every rule's severity to "warn". Combined with only 1 of the 25 members that
+ * lint passing `--max-warnings 0`, it meant no lint run in this workspace could
+ * fail — including `rules-of-hooks`, which `layouts` and `api` deliberately
+ * raise to "error" because a hook below an early return is React #310 in
+ * production. Removed 2026-09-09; the severities below are now the real ones.
+ *
  * @type {import("eslint").Linter.Config[]}
  * */
 export const config = [
@@ -18,19 +24,25 @@ export const config = [
       turbo: turboPlugin,
     },
     rules: {
-      "turbo/no-undeclared-env-vars": "warn",
+      // "error": an env var outside the cache key means turbo can hand back a
+      // build made with a different value — a wrong artifact that looks cached
+      // and correct. `NEXT_PUBLIC_*` is inlined at build time, so this is not
+      // hypothetical.
+      "turbo/no-undeclared-env-vars": "error",
     },
   },
   {
     rules: {
-      // A leading underscore is how this repo already writes "deliberately
+      // "error", because this is not style: it found a `startTime` in `nextjs`'s
+      // health route that was captured and never reported, dropping the duration
+      // the endpoint was meant to return.
+      //
+      // The ignore patterns encode how this repo already writes "deliberately
       // unused" — an interface method that must keep its signature, a caught
-      // error nobody inspects. `typescript-eslint`'s default knows nothing
-      // about that, so it reported the convention itself as a finding, and in
-      // a package linting with `--max-warnings 0` that made the intended
-      // spelling the failing one.
+      // error nobody inspects. Without them the convention itself reports as a
+      // finding, making the intended spelling the failing one.
       "@typescript-eslint/no-unused-vars": [
-        "warn",
+        "error",
         {
           argsIgnorePattern: "^_",
           varsIgnorePattern: "^_",
@@ -55,8 +67,11 @@ export const config = [
     // with a reason.
     files: ["**/*.{ts,tsx,js,jsx}"],
     rules: {
+      // "error": a raw color scale does not adapt to theme or preset, and the
+      // failure is invisible — the component just renders the wrong color in
+      // dark mode. Genuine exceptions disable on the line with a reason.
       "no-restricted-syntax": [
-        "warn",
+        "error",
         {
           selector:
             "Literal[value=/(bg|text|border|ring|fill|stroke|from|to|via|divide|outline|decoration|accent|caret|shadow)-(red|orange|amber|yellow|lime|green|emerald|teal|cyan|sky|blue|indigo|violet|purple|fuchsia|pink|rose|slate|gray|zinc|neutral|stone)-[0-9]/]",
@@ -72,11 +87,6 @@ export const config = [
       ],
     },
   },
-  {
-    plugins: {
-      onlyWarn,
-    },
-  },
   {
     ignores: ["dist/**"],
   },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@djangocfg/eslint-config",
-  "version": "2.1.542",
+  "version": "2.1.543",
   "description": "Shared ESLint configurations for Next.js, React, and TypeScript projects with best practices and Prettier integration",
   "keywords": [
     "eslint",
@@ -44,7 +44,6 @@
     "@next/eslint-plugin-next": "^15.5.20",
     "eslint": "^9.39.5",
     "eslint-config-prettier": "^10.1.8",
-    "eslint-plugin-only-warn": "^1.2.1",
     "eslint-plugin-react": "^7.37.5",
     "eslint-plugin-react-hooks": "^5.2.0",
     "eslint-plugin-turbo": "^2.10.4",