> 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/0088-to-0723/aur0713.md).

# AUR0713

Template compilation error: unknown binding command "yyyy".

### **Error message**

Template compilation error: unknown binding command: "{{0}}".{{0:bindingCommandHelp}}

### **Parameters**

1. `commandName`: The name of the unrecognized binding command.

### Error explanation

This error occurs during template compilation when an attribute uses a binding command (the part after the dot, like `.bind`, `.trigger`, `.for`) that is not registered or known to the template compiler. This could be due to a typo, using a command that doesn't exist, or forgetting to register a custom binding command.

The error message may also include additional help text (after the period) for common mistakes, such as suggesting `.trigger` for the removed `.delegate` command, or suggesting lambdas for the removed `.call` command.

### Common causes

* A typo in the binding command name (e.g., `value.bnd` instead of `value.bind`).
* Using a binding command that does not exist or is not registered (e.g., `value.nonexistent`).
* Forgetting to register a custom binding command via application configuration or `@bindingCommand` decorator.
* Attempting to use Aurelia v1 binding commands like `.delegate` or `.call` without appropriate compatibility configuration.

### How to fix

* Correct any typos in the binding command name. Standard commands include `bind`, `one-time`, `to-view`, `from-view`, `two-way`, `trigger`, `capture`, `for`, `ref`, `style`, `class`, `attr`, `spread`.
* Ensure any custom binding commands are properly defined and registered with the DI container.
* If migrating from v1, replace `.delegate` with `.trigger` and `.call` with lambda expressions or ensure compatibility settings are active.

### Example of Incorrect Usage:

```html
<!-- Error: Typo in binding command -->
<input value.bnd="message">

<!-- Error: Non-existent command -->
<button click.action="doSomething()"></button>

<!-- Error: V1 command without compat -->
<button click.delegate="handleClick()"></button>
```

### Example of Correct Usage:

```html
<!-- Correct command -->
<input value.bind="message">

<!-- Correct command -->
<button click.trigger="doSomething()"></button>

<!-- Correct command -->
<button click.trigger="handleClick()"></button>

<!-- Correct custom command (assuming 'my-cmd' is registered) -->
<div special.my-cmd="value"></div>
```


---

# 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/0088-to-0723/aur0713.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.