> 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/0901-to-0908/aur0904.md).

# AUR0904

Invalid dialog configuration. Specify default renderer or use the DialogConfigurationStandard/DialogConfigurationClassic export.

### **Error message**

Invalid dialog configuration. Specify default renderer or use the DialogConfigurationStandard/DialogConfigurationClassic export.

### **Parameters**

None

### Error explanation

This error occurs when you register `DialogConfiguration` (the base/no-op dialog configuration) without providing a renderer. `DialogConfiguration` exists as a starting point for building a custom configuration, but it intentionally throws unless you specify at least a default renderer.

### Common causes

* Registering `DialogConfiguration` instead of `DialogConfigurationStandard` or `DialogConfigurationClassic`.
* Customizing dialog settings but never setting `settings.renderer`.

### How to fix

* **Use a built-in configuration (recommended):**

  ```typescript
  import { DialogConfigurationClassic, DialogConfigurationStandard } from '@aurelia/dialog';

  // In your main configuration
  container.register(DialogConfigurationStandard); // or DialogConfigurationClassic
  ```
* **Or customize and provide a renderer:**

  ```typescript
  import { DialogConfiguration } from '@aurelia/dialog';
  import { MyDialogDomRenderer } from './my-dialog-dom-renderer';

  container.register(DialogConfiguration.customize(settings => {
    settings.renderer = MyDialogDomRenderer;
    // ...other settings...
  }));
  ```

### Debugging tips

* Check your application's main configuration file (e.g., `main.ts` or where you configure Aurelia).
* Verify you are registering `DialogConfigurationStandard` or `DialogConfigurationClassic` (or a customized `DialogConfiguration` that sets `settings.renderer`).
* If you have multiple containers (e.g., tests), ensure dialog configuration is registered in the container used by your app.


---

# 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/0901-to-0908/aur0904.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.