# debug.trace

Detail for working on the code

Profile: [Logs](https://www.prongs.dev/docs/intents/logs.md) · Written with: [`log()`](https://www.prongs.dev/docs/profiles/logs.md) · Level: `debug` · Production: off

## Example

```ts
log('debug.trace', 'Resolved page', { slug: 'about', tookMs: 12 });
```

Writes, in development only

```ts
{
  "intent": "debug.trace",
  "level": "debug",
  "alert": false,
  "message": "Resolved page",
  "data": {
    "slug": "about",
    "tookMs": 12
  },
  "time": "2026-10-09T12:00:00.000Z"
}
```

## Choosing between neighbours

Find the row that describes your case, and use the intent on the right.

| If it is for… | Use |
|---|---|
| Detail for working on the code | `debug.trace` (this page) |
| Anything someone running the app needs to see | [`job.finished`](https://www.prongs.dev/docs/intents/job/finished.md) |

## Connections

Declared in the registry, both directions. Where an intent is used in your own code is something check and the gallery see; this site has no app code.

- Built from: [`level.debug`](https://www.prongs.dev/docs/intents/logs.md#level-debug)

## For registry authors

**Starter intents.** These are the intents `prongs add logs` puts in your registry. Change levels through the [`level.*`](https://www.prongs.dev/docs/intents/logs.md#level) intents, and point [`log()`](https://www.prongs.dev/docs/profiles/logs.md) at your logger.

The entry `prongs add logs` writes into your registry. Change the level through its [`level.*`](https://www.prongs.dev/docs/intents/logs.md#level) ref.

```ts
'debug.trace': {
  kind: 'semantic',
  description: 'Detail for working on the code',
  refs: ['level.debug'],
  notFor: [
    {
      context: 'anything someone running the app needs to see',
      instead: 'job.finished',
    },
  ],
},
```