> 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/aur0701.md).

# AUR0701

Template compilation error in element "{{0:name}}": the root \<template> cannot be a local element template.

### **Error message**

Template compilation error in element "{{0:name}}": the root `<template>` cannot be a local element template.

### **Parameters**

1. `name`: The name of the custom element being compiled.

### Error explanation

This error occurs when the template compiler encounters the `as-custom-element` attribute on the root `<template>` tag of a custom element's definition. The `as-custom-element` attribute is used to define local elements (elements defined within another element's template), and it cannot be applied to the main template of a custom element.

### Common causes

* Adding `as-custom-element="some-name"` to the main `<template>` tag of a component's HTML file.

### How to fix

* Remove the `as-custom-element` attribute from the root `<template>` tag of your component's template.
* If you intend to define a local element, ensure the `<template as-custom-element="...">` tag is nested inside the main `<template>` tag of the parent component.

### Example of Incorrect Usage:

```html
<!-- my-component.html -->
<template as-custom-element="this-is-wrong"> <!-- Error: as-custom-element on root template -->
  <div>Hello</div>
</template>
```

### Example of Correct Usage (Local Element):

```html
<!-- parent-component.html -->
<template>
  <div>Parent Content</div>

  <!-- Define a local element -->
  <template as-custom-element="local-element">
    <div>This is the local element content</div>
  </template>

  <!-- Use the local element -->
  <local-element></local-element>
</template>
```


---

# 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/aur0701.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.