# ErrorsConfig

`interface` in `types` · v0.7.1

<https://docs.seedcord.org/packages/types/0.7.1/interfaces/errors-config>

Settings for how the framework renders errors and reports faults.

```ts
interface ErrorsConfig
```

## Properties

### defaultError

```ts
defaultError: new (uuid: UUID) => RenderableNotice
```

Class the framework constructs to render an unknown, non-denial fault. It receives the fault's tracking uuid.

### errorStack

```ts
errorStack: boolean;
```

Whether to show the error stack trace in the terminal for an unknown fault.

### ignoreApiCodes

```ts
ignoreApiCodes: readonly (number | string)[]
```

discord.js API error codes the interaction error path swallows quietly instead of reporting a fault, for a code thrown by the handler's own work. When empty, every such code reports and a real bug (a double ack from a misplaced defer) surfaces. Add a code here to swallow it once you have confirmed it is an expected dead end in your bot. A swallowed code still debug-logs.

The reply sender always swallows the harmless reply-token codes on its own send for safety, independent of this list, so the error path never crashes.

### ignoreEventApiCodes

```ts
ignoreEventApiCodes: readonly (number | string)[]
```

discord.js API error codes the event error path swallows quietly instead of reporting a fault. Discord delivers dead resources on events (a reaction on a deleted message, a member that just left), so a handler's own fetch can throw a gone-resource error.

When empty, a dead resource reports (throttled to one per minute per handler) until you confirm it is an expected dead end and add the code here, for example Unknown Message (10008), Unknown Member (10007), Unknown User (10013). A swallowed code still debug-logs.