import type { ComponentDefinition } from './component-types'; import { type PropsDef } from './props'; /** * Phase transitions: * * ``` * UNINITIALIZED ──_runSetup()──► SETUP_DONE * SETUP_DONE ──disconnectedCallback()──► UNMOUNTED ──(reset)──► UNINITIALIZED * ``` * * `generation` increments on every disconnect. Scheduled mount callbacks capture * it so callbacks belonging to a disconnected instance cannot run after a * reconnect (see `_isStale`). * * Why this lives on the class instead of a standalone pure reducer: every * transition here is triggered by running actual user code (`def.setup()`, * `onMounted` callbacks) inside a reactive `scope.run()` + `runWithContext()` * — there is no meaningful "decide the next phase" step that can be separated * from "run the side-effecting thing that produces the phase change" without * introducing a data-only effect-description layer that this package has no * other use for. That's why the methods below stay as direct, readable * procedural steps instead of a reducer + effect interpreter. */ export declare class BaseElement extends HTMLElement { static _definition: ComponentDefinition; static _normalizedPropDefs: PropsDef> | undefined; static formAssociated: boolean; static observedAttributes: string[]; private _component; constructor(); connectedCallback(): void; attributeChangedCallback(name: string, oldValue: string | null, newValue: string | null): void; disconnectedCallback(): void; /** Dispose one connection's resources before its state can be rebuilt. */ private _resetSetupState; /** * Native form-association lifecycle callback — the browser calls this on every * `formAssociated: true` element inside a `
` when that form is reset. * Runs every `onFormReset()` callback registered during `setup()`. */ formResetCallback(): void; private _reportLifecycleError; private _runSetup; private _isStale; private _applyResult; private _init; private _applyStyles; private _mountTemplate; private _scheduleMountCallbacks; } //# sourceMappingURL=base-element.d.ts.map