> For the complete documentation index, see [llms.txt](https://docs.aurelia.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aurelia.io/developer-guides/error-messages.md).

# Errors

## Error message format

Encountered an error and looking for answers? You've come to the right place.

{% hint style="danger" %}
This section is a work in progress and not yet complete. If you would like to help us document errors in Aurelia, we welcome all contributions.
{% endhint %}

Coded errors in Aurelia use the format `AURxxxx:yyyy` where:

* `AUR` is the prefix to indicate it's an error from Aurelia
* `xxxx` is the code
* `:` is the delimiter between the prefix, code and the dynamic information associated with the error
* `yyyy` is the extra information, or parameters related to the error

## Enabling development debug information

When using production builds of the core Aurelia packages, you may see an error message like `AUR0015:abcxyz`, which can be hard to interpret during development.

In development builds, Aurelia errors typically include a human-readable message and a link to the corresponding documentation page.

### Vite

`@aurelia/vite-plugin` automatically picks the development build when `process.env.NODE_ENV` is not `production`. You can also override this using the `useDev` option:

```ts
import { defineConfig } from 'vite';
import aurelia from '@aurelia/plugin-vite';

export default defineConfig({
  plugins: [
    aurelia({ useDev: true }),
  ],
});
```

### Webpack

Add an alias to `resolve.alias` in your `webpack.config.js`, similar to the scaffolding template at:

`https://github.com/aurelia/new/blob/06f06862bab5f7b13107237a69cf59de1385d126/webpack/webpack.config.js#L117-L123`

### Other bundlers/dev servers

The `dist` folder of an Aurelia core package looks like this:

```
dist
  |
  + -> cjs
  |     |
  |     + -> index.cjs
  |     + -> index.dev.cjs
  |
  + -> esm
        |
        + -> index.mjs
        + -> index.dev.mjs
```

Whenever there's a request to retrieve `dist/esm/index.mjs`, you can redirect it to `dist/esm/index.dev.mjs`.

## Error docs index

In development builds, follow the documentation link printed in the error message. Some `AURxxxx` codes are reused across packages; the link printed by the package is the authoritative source.

### Core

* `@aurelia/kernel` — [0001-to-0023](/developer-guides/error-messages/0001-to-0023.md)
* `@aurelia/expression-parser` — [0151-to-0179](/developer-guides/error-messages/0151-to-0179.md)
* `@aurelia/runtime` — [0203-to-0227](/developer-guides/error-messages/0203-to-0227.md)
* `@aurelia/template-compiler` — [0088-to-0723](/developer-guides/error-messages/0088-to-0723.md)
* `@aurelia/runtime-html` — [runtime-html](/developer-guides/error-messages/runtime-html.md)
* `@aurelia/platform` — [platform](/developer-guides/error-messages/platform.md)

### Routing

* `@aurelia/router` — [router](/developer-guides/error-messages/router.md)

### Optional packages

* `@aurelia/dialog` — [0901-to-0908](/developer-guides/error-messages/0901-to-0908.md)
* `@aurelia/i18n` — [4000-to-4002](/developer-guides/error-messages/4000-to-4002.md)
* `@aurelia/validation` — [4100-to-4106](/developer-guides/error-messages/4100-to-4106.md)
* `@aurelia/validation-html` — [4200-to-4206](/developer-guides/error-messages/4200-to-4206.md)
* `@aurelia/fetch-client` — [5000-to-5008](/developer-guides/error-messages/5000-to-5008.md)
* `@aurelia/ui-virtualization` — [ui-virtualization](/developer-guides/error-messages/ui-virtualization.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aurelia.io/developer-guides/error-messages.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.