fix: eslint-config-next being evaluated even if not being used

Author: mfeltscher

src/configs.ts

@@ -72,16 +72,18 @@ export const flatConfigTypescript = (rulesOnly = false) =>
     baseConfig,
   ]);
 
-export const flatConfigReact = defineConfig([
-  ...flatConfigTypescript(),
-  reactPlugin.configs.flat.recommended,
-  reactPlugin.configs.flat['jsx-runtime'],
-  reactHooks.configs.flat.recommended,
-  reactConfig,
-]);
+export const flatConfigReact = () =>
+  defineConfig([
+    ...flatConfigTypescript(),
+    reactPlugin.configs.flat.recommended,
+    reactPlugin.configs.flat['jsx-runtime'],
+    reactHooks.configs.flat.recommended,
+    reactConfig,
+  ]);
 
-export const flatConfigNext = defineConfig([
-  ...createRequire(import.meta.url)('eslint-config-next/core-web-vitals'),
-  ...flatConfigTypescript(true),
-  reactConfig,
-]);
+export const flatConfigNext = () =>
+  defineConfig([
+    ...createRequire(import.meta.url)('eslint-config-next/core-web-vitals'),
+    ...flatConfigTypescript(true),
+    reactConfig,
+  ]);

src/index.ts

@@ -6,9 +6,9 @@ export const config = (type: 'typescript' | 'react' | 'nextjs'): Linter.Config[]
     case 'typescript':
       return flatConfigTypescript();
     case 'react':
-      return flatConfigReact;
+      return flatConfigReact();
     case 'nextjs':
-      return flatConfigNext;
+      return flatConfigNext();
     default:
       throw new Error(`Unknown config type: ${type}`);
   }