> 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/runtime-html/aur0830.md).

# AUR0830

## Error Message

`AUR0830: Invalid portal target, position "<position>" needs a target that has a parent node.`

Where `<position>` is `beforebegin` or `afterend`.

## Description

The `portal` attribute places its content relative to the target element. With `position: beforebegin` or `position: afterend` the content goes next to the target, inside the target's parent. If the target has no parent, there is nowhere to put the content.

The portal checks this before it moves anything. When the error comes from a target or position change, the content stays where it was.

## Cause

The resolved target is an element that is not attached anywhere, for example one created with `document.createElement()` and not inserted yet, or one that has been removed from the DOM.

```typescript
export class MyComponent {
  // created, but never inserted into the document
  target = document.createElement('div');
}
```

```html
<div portal="target.bind: target; position: afterend">Portal content</div>
```

## Solution

* Insert the target element into the DOM before the portal attaches or before you bind it.
* Use `position: beforeend` or `position: afterbegin` if you want the content inside the target. Those positions only need the target itself.
* If the target is created later, keep `target` unset or bound to an attached element until it is ready.


---

# 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/runtime-html/aur0830.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.
