next.js

741d095a - backport(15.3): document turbopack trace viewer (#78184) (#80589)

backport(15.3): document turbopack trace viewer (#78184) (#80589) Backports https://github.com/vercel/next.js/pull/78184 (@timneutkens) User request: (https://vercel.slack.com/archives/C06CUNEC64D/p1750069211569019) > could the change from `next internal turbo-trace-server` to `next internal trace` be backported to a non-canary Next.js version? (to align with the published docs suggestion) > > currently, the docs say "You can interpret the file using `next internal trace [path-to-file]`:" ... and then further down "On versions where `trace` is not available, the command was named `turbo-trace-server`" ... which means that anyone on non-canary versions following the docs right now will receive `error: unknown command 'trace'` > > https://nextjs.org/docs/app/guides/local-development#turbopack-tracing The `mdx` change here isn't really relevant, since we don't build docs from this branch, but it merges cleanly, so it's harmless. Co-authored-by: Tim Neutkens <tim@timneutkens.nl>