Unverified Commit 0e678db5 authored by Tim Neutkens's avatar Tim Neutkens Committed by GitHub

Add path to export-page (#39893)

Adds a missing tag in the trace-to-tree helper that allows you to see the path of the `export-page` span.


## Bug

- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Errors have helpful link attached, see `contributing.md`

## Feature

- [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR.
- [ ] Related issues linked using `fixes #number`
- [ ] Integration tests added
- [ ] Documentation added
- [ ] Telemetry added. In case of a feature if it's used or not.
- [ ] Errors have helpful link attached, see `contributing.md`

## Documentation / Examples

- [ ] Make sure the linting passes by running `pnpm lint`
- [ ] The examples guidelines are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing.md#adding-examples)
parent 34e10f30
...@@ -127,6 +127,9 @@ const formatEvent = (event) => { ...@@ -127,6 +127,9 @@ const formatEvent = (event) => {
case 'hot-reloader': case 'hot-reloader':
head = `${chalk.bold.green(`hot reloader`)}` head = `${chalk.bold.green(`hot reloader`)}`
break break
case 'export-page':
head = `${event.name} ${event.tags.path} ${formatTimes(event)}`
break
default: default:
if (event.name.startsWith('build-module-')) { if (event.name.startsWith('build-module-')) {
const { mergedChildren, childrenTimings, packageName } = event const { mergedChildren, childrenTimings, packageName } = event
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment