> klz-cables-nextjs@1.0.0 lint /Users/marcmintel/Projects/klz-2026 > eslint . (node:66439) ESLintEnvWarning: /* eslint-env */ comments are no longer recognized when linting with flat config and will be reported as errors as of v10.0.0. Replace them with /* global */ comments or define globals in your config file. See https://eslint.org/docs/latest/use/configure/migration-guide#eslint-env-configuration-comments for details. Found in /Users/marcmintel/Projects/klz-2026/.lintstagedrc.cjs at line 2. (Use `node --trace-warnings ...` to show where the warning was created) (node:66439) ESLintEnvWarning: /* eslint-env */ comments are no longer recognized when linting with flat config and will be reported as errors as of v10.0.0. Replace them with /* global */ comments or define globals in your config file. See https://eslint.org/docs/latest/use/configure/migration-guide#eslint-env-configuration-comments for details. Found in /Users/marcmintel/Projects/klz-2026/commitlint.config.cjs at line 2. (node:66439) ESLintEnvWarning: /* eslint-env */ comments are no longer recognized when linting with flat config and will be reported as errors as of v10.0.0. Replace them with /* global */ comments or define globals in your config file. See https://eslint.org/docs/latest/use/configure/migration-guide#eslint-env-configuration-comments for details. Found in /Users/marcmintel/Projects/klz-2026/postcss.config.cjs at line 2. (node:66439) ESLintEnvWarning: /* eslint-env */ comments are no longer recognized when linting with flat config and will be reported as errors as of v10.0.0. Replace them with /* global */ comments or define globals in your config file. See https://eslint.org/docs/latest/use/configure/migration-guide#eslint-env-configuration-comments for details. Found in /Users/marcmintel/Projects/klz-2026/tailwind.config.cjs at line 2. /Users/marcmintel/Projects/klz-2026/.lintstagedrc.cjs 3:14 error A `require()` style import is forbidden @typescript-eslint/no-require-imports /Users/marcmintel/Projects/klz-2026/app/[locale]/blog/[slug]/page.tsx 2:8 warning 'Script' is defined but never used @typescript-eslint/no-unused-vars 4:10 warning 'getBreadcrumbSchema' is defined but never used @typescript-eslint/no-unused-vars 4:41 warning 'LOGO_URL' is defined but never used @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/app/[locale]/blog/page.tsx 63:15 warning Using `` could result in slower LCP and higher bandwidth. Consider using `` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element 148:25 warning Using `` could result in slower LCP and higher bandwidth. Consider using `` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element /Users/marcmintel/Projects/klz-2026/app/[locale]/layout.tsx 81:12 warning 'e' is defined but never used @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/app/[locale]/page.tsx 70:12 warning 'err' is defined but never used @typescript-eslint/no-unused-vars 74:14 warning 'e' is defined but never used @typescript-eslint/no-unused-vars 75:12 warning 'key' is defined but never used. Allowed unused args must match /^_/u @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/app/[locale]/products/[...slug]/page.tsx 1:8 warning 'Script' is defined but never used @typescript-eslint/no-unused-vars 3:10 warning 'getBreadcrumbSchema' is defined but never used @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/app/errors/api/relay/route.ts 28:11 warning 'header' is assigned a value but never used @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/components/CMSConnectivityNotice.tsx 4:34 warning 'Database' is defined but never used @typescript-eslint/no-unused-vars 8:10 warning 'status' is assigned a value but never used @typescript-eslint/no-unused-vars 35:16 warning 'err' is defined but never used @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/components/Header.tsx 36:7 warning Error: Calling setState synchronously within an effect can trigger cascading renders Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following: * Update external systems with the latest state from React. * Subscribe for updates from some external system, calling setState in a callback function when external state changes. Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect). /Users/marcmintel/Projects/klz-2026/components/Header.tsx:36:7 34 | useEffect(() => { 35 | if (isMobileMenuOpen) { > 36 | setIsMobileMenuOpen(false); | ^^^^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect 37 | } 38 | }, [pathname, isMobileMenuOpen]); 39 | react-hooks/set-state-in-effect 116:37 warning 'idx' is defined but never used. Allowed unused args must match /^_/u @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx 24:5 warning Error: Calling setState synchronously within an effect can trigger cascading renders Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following: * Update external systems with the latest state from React. * Subscribe for updates from some external system, calling setState in a callback function when external state changes. Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect). /Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx:24:5 22 | 23 | useEffect(() => { > 24 | setMounted(true); | ^^^^^^^^^^ Avoid calling setState() directly within an effect 25 | return () => setMounted(false); 26 | }, []); 27 | react-hooks/set-state-in-effect 62:9 warning Error: Calling setState synchronously within an effect can trigger cascading renders Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following: * Update external systems with the latest state from React. * Subscribe for updates from some external system, calling setState in a callback function when external state changes. Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect). /Users/marcmintel/Projects/klz-2026/components/Lightbox.tsx:62:9 60 | const index = parseInt(photoParam, 10); 61 | if (!isNaN(index) && index >= 0 && index < images.length) { > 62 | setCurrentIndex(index); | ^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect 63 | } 64 | } 65 | }, [searchParams, images.length]); react-hooks/set-state-in-effect /Users/marcmintel/Projects/klz-2026/components/OGImageTemplate.tsx 49:11 warning Using `` could result in slower LCP and higher bandwidth. Consider using `` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element /Users/marcmintel/Projects/klz-2026/components/home/GallerySection.tsx 30:38 warning Error: Calling setState synchronously within an effect can trigger cascading renders Effects are intended to synchronize state between React and external systems such as manually updating the DOM, state management libraries, or other platform APIs. In general, the body of an effect should do one or both of the following: * Update external systems with the latest state from React. * Subscribe for updates from some external system, calling setState in a callback function when external state changes. Calling setState synchronously within an effect body causes cascading renders that can hurt performance, and is not recommended. (https://react.dev/learn/you-might-not-need-an-effect). /Users/marcmintel/Projects/klz-2026/components/home/GallerySection.tsx:30:38 28 | const index = parseInt(photoParam, 10); 29 | if (!isNaN(index) && index >= 0 && index < images.length) { > 30 | if (lightboxIndex !== index) setLightboxIndex(index); | ^^^^^^^^^^^^^^^^ Avoid calling setState() directly within an effect 31 | if (!lightboxOpen) setLightboxOpen(true); 32 | } 33 | } react-hooks/set-state-in-effect /Users/marcmintel/Projects/klz-2026/components/home/RecentPosts.tsx 37:21 warning Using `` could result in slower LCP and higher bandwidth. Consider using `` from `next/image` or a custom image loader to automatically optimize images. This may incur additional usage or cost from your provider. See: https://nextjs.org/docs/messages/no-img-element @next/next/no-img-element /Users/marcmintel/Projects/klz-2026/lib/config.ts 5:10 warning 'env' is defined but never used @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/lib/mail/mailer.ts 4:10 warning 'ReactElement' is defined but never used @typescript-eslint/no-unused-vars /Users/marcmintel/Projects/klz-2026/middleware.ts 2:10 warning 'NextResponse' is defined but never used @typescript-eslint/no-unused-vars 33:12 warning 'publicHostname' is assigned a value but never used @typescript-eslint/no-unused-vars ✖ 27 problems (1 error, 26 warnings)  ELIFECYCLE  Command failed with exit code 1.