Framework Direction

Effuse core is moving toward a capability-first framework model: typed layers, local layer aliases in define({ script }), shared hook/component layer DX, and layer-owned server APIs/actions with client-side action helpers and server manifests for typed clients. Server handlers also receive validation helpers for params, query, headers, JSON bodies, and form data so request contracts live next to the layer that owns the capability. Typed server errors can be returned with ctx.response.error, thrown with LayerServerError, and narrowed from action clients through LayerActionError<T>. Layer-owned server routes and actions can also declare middleware plus cache, CORS, runtime, region, and duration metadata that flows into responses and the server manifest.

Read the detailed proposal in FRAMEWORK_DX_PROPOSAL.md.

Browser Hooks

Core browser hooks keep server rendering and the browser's pre-mount hydration pass deterministic. Storage reads, DOM listeners, element-ref resolution, and observer construction begin after component mount.

| Hook | Standalone cleanup | | --- | --- | | useLocalStorage, useSessionStorage | result.dispose() | | useOnClickOutside | returned stop() function | | useResizeObserver, useIntersectionObserver | signal.stop() |

const size = useResizeObserver(() => panelRef);
const preferences = useLocalStorage('preferences', defaults);

Component-owned resources stop automatically during unmount. Call the cleanup API when using a hook outside a component. A storage write requested before mount updates the signal immediately and is flushed at mount without first replacing it from the stored value.