Core concepts

Terminology and session model for @jayoncode/browser-lifecycle.

Previous: Overview · Next: Tutorial

Problem → approach

Scattered browser listeners	With Browser Lifecycle
document.addEventListener("visibilitychange", …) in every feature	One session, typed page:visible / page:hidden events
Duplicate online/offline handlers across modules	Normalized connectivity:* events + snapshot
No single place to read “current tab state”	getSnapshot() — readonly consolidated state
Leaked listeners on SPA route changes	dispose() tears down modules and subscriptions

Session

const lifecycle = createBrowserLifecycle({ autoStart: true });

One instance per browser tab. Share it via app context — do not create one per component.

API map

Concept	Responsibility	API
Session	Lifecycle boundary	createBrowserLifecycle()
Event	Normalized browser signal	lifecycle.on("page:hidden", …)
Snapshot	Current module state	lifecycle.getSnapshot()
Module	Visibility, focus, idle, etc.	Configuration + typed events
Plugin	Cross-cutting extension	Plugin registration API

Session phases

Phase	Meaning
created	Constructed, not listening
running	Active listeners
stopped	Paused
disposed	Torn down — do not reuse

Next steps

Goal	Guide
Integration walkthrough	Tutorial
Page visibility	Visibility
Event subscription	Events

State explorer →