Flarum (2.x)
    Preparing search index...

    The Page component

    Hierarchy (View Summary)

    Index
    busy: boolean = false
    checking: boolean = false
    dismissed: boolean = false
    driver: string | null = null
    firstLoad: boolean = true
    history: HistoryEntry[] = []
    host: HostReport | null = null
    installed: Installed[] = []
    loadError: string | null = null

    Set when the first load fails or never arrives, so the page can say so.

    loadErrorDetail: string | null = null

    The exception's own text, shown under the translated message when there is one.

    loads: {
        invalidate: () => void;
        isCurrent: (ticket: number) => boolean;
        next: () => number;
    } = ...

    Only the newest /state reply is used; see runState.requestSequence.

    loadTimeout: Timeout | null = null

    The 10-second safety net for the first load, cleared when the page goes.

    rollbackNote: string | null = null
    rollingBack: boolean = false

    An undo started from the History tab, while the run panel is dismissed.

    run: Run | null = null
    stale: boolean = false
    starting: boolean = false
    updates: Updates = ...
    DISMISS_KEY: string = 'extension-manager.dismissedRun'

    Dismissal is remembered against WHICH run, and it has to be remembered at all.

    dismissed is component state, so it was gone on the next page load and a finished run's panel came back every single time. Combined with the panel hiding the tabs, that meant one update run ever — even a successful one — left the page showing nothing but a week-old log, with no extension grid, no Update buttons and no way to reach them. Keyed by id so a NEW run is never silently pre-dismissed.

    • Raising a pin edits composer.json, so it is asked for in those words.

      The new version is NOT sent to the server. The request carries a yes, and the server takes the target from its own update check — so the only version a requirement can move to is the one on the card the admin just read. A version travelling from the browser into composer.json would be an arbitrary string from a client.

      Parameters

      Returns void

    • The installed tab: whether anything is newer, then Flarum itself, then anything to update, then the cards. The check comes first because it is what people come to this tab for; the sidebar already lists what is installed (ClaudiusH, 2026-10-09).

      Every entry is keyed AND the falsy ones are removed, because Mithril requires that in a fragment either every vnode has a key or none does — and a null counts as one without. updateAll() returns null when nothing has a newer version, so this array was legal on a forum with updates waiting and a TypeError on one that was up to date. It rendered nothing at all: the component threw during view, which on a Mithril page means the spinner that was already on screen simply stayed there.

      Which is to say the page was broken in its most ordinary state, and one load of it in a browser would have shown that immediately.

      Returns (Element | null)[]

    • The Extension Manager updating ITSELF leaves this page running the old version's code: the header still said v1.15.0 under a finished v1.16.1 update (ClaudiusH, 2026-10-07). So the page reloads, once per run and outcome. The finished panel comes straight back, because the run is on disk.

      Parameters

      • run: Run | null

      Returns void

    • Whether a run is still going.

      Only a LIVE run may take the page over. Hiding the grid while an update is applying is right — a row of Update buttons beside a running update invites a second one, and the honest answer to that is a refusal. Hiding it because a run finished yesterday is not: the log is worth keeping on screen, the rest of the page is worth having as well.

      Returns boolean

    • Parameters

      • packages: string[]
      • mode: RunMode = 'update'

        'install' adds a package that is not here yet. It is not cosmetic: composer update on an uninstalled package does nothing and exits 0, so a run in the wrong mode would pass every phase, change nothing, and report success.

      • repin: boolean = false
      • nightly: boolean = false

      Returns void

    • The run History may offer to undo: the latest one, when it finished or failed and its panel has been dismissed.

      Dismissing a failed run is remembered, and the panel held the only Roll back button, so a dismissed failure could no longer be undone from this page at all. Only the latest run, because that is the one the rollback endpoint undoes, and only while the panel is away, so there is never a second button for the same undo on screen.

      Returns string | null

    • Every package with a newer version, in one press.

      Resolved TOGETHER rather than as a queue of separate updates. Two extensions can each have a newer version and still be uninstallable side by side; asking Composer about all of them at once is the only way to find that out before anything moves, rather than halfway through the second one.

      Returns Element | null

    • One count everywhere: the extensions "Update all" would update. The tab badge and the line above counted every newer package, Flarum itself included, so they read 17 beside "Update all 16" and stayed one ahead after each update (ClaudiusH, 2026-10-09). Flarum has its own panel, and the line names it separately.

      Returns number