fix(nextjs): suppress Turbopack node:crypto export-star warning

Next.js 16 exits with code 1 when Turbopack encounters unhandled warnings. The node:crypto CJS module triggers an 'unexpected export *' warning through the image-proxy route because node:crypto exposes its API as CJS exports only available at runtime. The named imports used at runtime are fine — this is a static analysis limitation in Turbopack's ESM/CJS interop detection. Suppress via ignoreIssue (same pattern already used for the NFT list warning) until upstream resolves the detection in vercel/next.js.
2026-07-14 17:36:35 +02:00
3 changed files with 551 additions and 351 deletions
@@ -42,6 +42,13 @@ const nextConfig: NextConfig = {
        path: "**/*",
        title: "Encountered unexpected file in NFT list",
      },
+      {
+        // node:crypto is CJS; `export *` from it triggers a Turbopack warning
+        // that exits 1 in Next.js 16. Named imports in image-proxy are fine at
+        // runtime — suppress until upstream resolves the ESM/CJS detection.
+        path: "**/*",
+        title: "unexpected export *",
+      },
    ],
  },
  transpilePackages: ["@homarr/ui", "@homarr/notifications", "@homarr/modals", "@homarr/spotlight", "@homarr/widgets"],
@@ -177,7 +177,7 @@ catalog:
  tsdav: ^2.3.0
  tsx: 4.20.4
  turbo: ^2.10.4
-  typescript: "npm:@typescript/typescript6@^6.0.2"
+  typescript: ^7.0.2
  vite: ^8.1.4
  undici: 7.28.0
  use-deep-compare-effect: ^1.8.1