From 70af7dfe7bababea1c2fba281855825477686330 Mon Sep 17 00:00:00 2001 From: Thomas Camlong Date: Tue, 14 Jul 2026 17:36:35 +0200 Subject: [PATCH] fix(nextjs): suppress Turbopack node:crypto export-star warning MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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. --- apps/nextjs/next.config.ts | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/apps/nextjs/next.config.ts b/apps/nextjs/next.config.ts index 4ff31b9aa..11f424b7c 100644 --- a/apps/nextjs/next.config.ts +++ b/apps/nextjs/next.config.ts @@ -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"],