commit 051f308bcaea03c739f95c77d5118715c9c47b2d
parent 179a9171ac57f375e3157b433cf24b4d33571fb3
Author: I Mean I'm Just Saying <imeanimjustsaying@kiwifarms.st>
Date: Fri, 19 Jun 2026 17:20:23 -0400
Suppress harmless Turbopack NFT "whole project traced" build warning
Turbopack's file tracer conservatively globs the cwd because the server
code does legitimate runtime-dynamic fs reads it can't statically bound
(readdir(videoDir), per-job log reads, settings.json). The resulting
"Encountered unexpected file in NFT list / whole project was traced"
warning is a false positive: there is no `output: 'standalone'`, so the
.nft.json traces are never consumed at runtime.
Suppress it with a scoped `turbopack.ignoreIssue` rule (path + title) so
the build is clean while other Turbopack warnings still surface. Note the
option works in `next build` despite the docs implying dev-only.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Diffstat:
1 file changed, 15 insertions(+), 0 deletions(-)
diff --git a/editor/next.config.ts b/editor/next.config.ts
@@ -1,6 +1,21 @@
import type { NextConfig } from "next";
const nextConfig: NextConfig = {
+ turbopack: {
+ // Suppress the harmless "whole project was traced unintentionally" NFT
+ // warning. Turbopack's file tracer conservatively globs the cwd because our
+ // server code does legitimate runtime-dynamic fs reads it can't statically
+ // bound (e.g. readdir(videoDir), reading per-job logs, settings.json). We
+ // don't use `output: 'standalone'`, so the .nft.json traces are never
+ // consumed at runtime and the over-tracing is purely cosmetic. Scoped to
+ // this exact issue (path + title) so other Turbopack warnings still surface.
+ ignoreIssue: [
+ {
+ path: "**/next.config.ts",
+ title: "Encountered unexpected file in NFT list",
+ },
+ ],
+ },
transpilePackages: ["yt-dlp-transcript-common"],
serverExternalPackages: ["lmdb", "msgpackr", "msgpackr-extract"],
experimental: {