@open-turo/eslint-config-react 18.0.8 → 19.0.0

package/docs/breaking-changes/v19.md

@@ -0,0 +1,6 @@
+# Breaking changes in v19
+
+- Sets `react-hooks/todo` to error on React Compiler de-opt syntax.
+  - As a work-around, either `// eslint-disable` existing violations, or re-write code to use syntax that allows for compiler optimization.
+- Ports over changes from `recommended.cjs` to `index.cjs`, as we have not kept rules in sync.
+  - The breaking changes from v18 will surface in usages that use the ESLint v9 flat config instead of the legacy `/recommended` config.

package/index.cjs

@@ -89,6 +89,29 @@ module.exports = function config(options = {}) {
             specialLink: ["to"],
           },
         ],
+        /**
+         * We enforce this as error to be more thoroughly React Compiler-compliant.
+         *
+         * {@link https://react.dev/reference/eslint-plugin-react-hooks/lints/exhaustive-deps docs}
+         */
+        "react-hooks/exhaustive-deps": "error",
+        /**
+         * Set as "warn" by default, we want to error on incompatible library APIs for dev visibility (to require // eslint-disable)
+         *
+         * {@link https://react.dev/reference/eslint-plugin-react-hooks/lints/incompatible-library docs}
+         */
+        "react-hooks/incompatible-library": "error",
+        /**
+         * Technically an undocumented rule, this rule surfaces in syntax that causes the React Compiler to de-opt.
+         * Raising errors increases visibility into whether a component/hook as written cannot be optimized.
+         */
+        "react-hooks/todo": "error",
+        /**
+         * Not a rule we expect to see, but all other rules are set to "error", and so we set this one to "error" too (to require // eslint-disable)
+         *
+         * {@link https://react.dev/reference/eslint-plugin-react-hooks/lints/unsupported-syntax docs}
+         */
+        "react-hooks/unsupported-syntax": "error",
         // don't force .jsx extension
         "react/jsx-filename-extension": "off",
         // In TS you must use the Fragment syntax instead of the shorthand

package/package.json

@@ -3,15 +3,15 @@
   "description": "Turo eslint configuration for react",
   "type": "module",
   "dependencies": {
-    "@open-turo/eslint-config-typescript": "18.1.30",
+    "@open-turo/eslint-config-typescript": "18.1.31",
     "eslint-plugin-jsx-a11y": "6.10.2",
     "eslint-plugin-react": "7.37.5",
     "eslint-plugin-react-hooks": "7.0.1",
     "globals": "17.0.0",
-    "typescript-eslint": "8.52.0"
+    "typescript-eslint": "8.53.0"
   },
   "devDependencies": {
-    "@types/react": "19.2.7",
+    "@types/react": "19.2.8",
     "eslint": "9.39.2",
     "jest": "30.2.0",
     "prettier": "3.7.4",
@@ -48,5 +48,5 @@
     "access": "public"
   },
   "repository": "https://github.com/open-turo/eslint-config-react",
-  "version": "18.0.8"
+  "version": "19.0.0"
 }

package/recommended.cjs

@@ -49,6 +49,11 @@ module.exports = {
      * {@link https://react.dev/reference/eslint-plugin-react-hooks/lints/incompatible-library docs}
      */
     "react-hooks/incompatible-library": "error",
+    /**
+     * Technically an undocumented rule, this rule surfaces in syntax that causes the React Compiler to de-opt.
+     * Raising errors increases visibility into whether a component/hook as written cannot be optimized.
+     */
+    "react-hooks/todo": "error",
     /**
      * Not a rule we expect to see, but all other rules are set to "error", and so we set this one to "error" too (to require // eslint-disable)
      *

package/test/__snapshots__/test.spec.js.snap

@@ -8035,6 +8035,9 @@ exports[`validate config the legacy recommended config is correct 1`] = `
   "react-hooks/static-components": [
     "error",
   ],
+  "react-hooks/todo": [
+    "error",
+  ],
   "react-hooks/unsupported-syntax": [
     "error",
   ],