From 38850bf1eec258fb1f95236051feb03e5b3d04eb Mon Sep 17 00:00:00 2001 From: Delba de Oliveira <32464864+delbaoliveira@users.noreply.github.com> Date: Thu, 11 Apr 2024 10:55:18 +0100 Subject: [PATCH] Docs: Instructions on how to generate turbopack trace file (#64325) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Balázs Orbán --- docs/04-architecture/turbopack.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/04-architecture/turbopack.mdx b/docs/04-architecture/turbopack.mdx index 3d771592276cb..e36d9ba360e3f 100644 --- a/docs/04-architecture/turbopack.mdx +++ b/docs/04-architecture/turbopack.mdx @@ -54,3 +54,9 @@ These features are currently not supported: - We are currently not planning to support Yarn PnP in Next.js with Turbopack. - [`experimental.urlImports`](/docs/app/api-reference/next-config-js/urlImports) - We are currently not planning to support `experimental.urlImports` in Next.js with Turbopack. + +## Generating Trace Files + +Trace files allow the Next.js team to investigate and improve performance metrics and memory usage. To generate a trace file, append `NEXT_TURBOPACK_TRACING=1` to the `next dev --turbo` command, this will generate a `.next/trace.log` file. + +When reporting issues related to Turbopack performance and memory usage, please include the trace file in your [GitHub](https://github.com/vercel/next.js) issue.