fix: add outputFileTracingExcludes to optimize Turbopack memory tracing
This commit is contained in:
@@ -46,6 +46,12 @@ const nextConfig: NextConfig = {
|
|||||||
// it from node_modules at runtime instead of trying to bundle it. Used by
|
// it from node_modules at runtime instead of trying to bundle it. Used by
|
||||||
// PLUGIN_DEV_DIR's on-the-fly bundler.
|
// PLUGIN_DEV_DIR's on-the-fly bundler.
|
||||||
serverExternalPackages: ["esbuild"],
|
serverExternalPackages: ["esbuild"],
|
||||||
|
// Sibling repos checked out under ./repos/ are unrelated source trees that
|
||||||
|
// Turbopack's NFT can otherwise rope into the trace when dynamic fs calls
|
||||||
|
// confuse it. Keeps the build from ballooning memory tracing dead code.
|
||||||
|
outputFileTracingExcludes: {
|
||||||
|
"*": ["./repos/**/*"],
|
||||||
|
},
|
||||||
turbopack: {
|
turbopack: {
|
||||||
root: import.meta.dirname,
|
root: import.meta.dirname,
|
||||||
},
|
},
|
||||||
|
|||||||
Reference in New Issue
Block a user