---
name: "up:framework:booted"
area: "API"
kind: "DOM event"
parent: "up.framework module"
visibility: "experimental"
url: "https://unpoly.com/api/up:framework:booted"
---
<nav aria-label="Unpoly docs">[All docs](https://unpoly.com/index.md) · [up.framework module](https://unpoly.com/api/up.framework.md)</nav>

# up:framework:booted

**This feature is experimental**. Please [share](https://github.com/unpoly/unpoly/discussions) your experiences so we know what to keep or change.

This event is emitted after Unpoly has [booted](https://unpoly.com/api/up.boot.md).

For most apps this event will be emitted in the same [task](https://jakearchibald.com/2015/tasks-microtasks-queues-and-schedules/) as [`DOMContentLoaded`](https://developer.mozilla.org/en-US/docs/Web/API/Window/DOMContentLoaded_event). All [compilers](https://unpoly.com/api/up.script.md) will already have run on the initial page content.

<nav aria-label="Guides">

- [Learn: Installation](https://unpoly.com/learn/install.md)

</nav>

---

## Event properties {#properties}

### event.mode {#event.mode}

(required)

A string indicating what caused Unpoly to boot.

If set to `'auto'`, Unpoly was booted automatically on `DOMContentLoaded`.

If set to `'manual'`, Unpoly was booted [manually](https://unpoly.com/api/up-boot-manual.md).

Type: string