JavaScript Observers
Observers deliver asynchronous notifications about layout, DOM changes, visibility, and performance entries without polling — essential for lazy-loading, responsive components, and instrumentation.
Always disconnect observers you create. Pair with AbortController patterns where possible.
info
| 1 | const io = new IntersectionObserver((entries) => { |
| 2 | for (const e of entries) { |
| 3 | if (e.isIntersecting) load(e.target); |
| 4 | } |
| 5 | }, { rootMargin: '200px' }); |
| 6 | io.observe(img); |
Fires when target visibility crosses thresholds within a root.
| 1 | const io = new IntersectionObserver((entries, obs) => { |
| 2 | for (const e of entries) { |
| 3 | if (!e.isIntersecting) continue; |
| 4 | e.target.src = e.target.dataset.src; |
| 5 | obs.unobserve(e.target); |
| 6 | } |
| 7 | }, { threshold: 0.25, rootMargin: '100px' }); |
Watches DOM tree changes. Powerful but easy to over-trigger — filter carefully.
| 1 | const mo = new MutationObserver((muts) => { |
| 2 | for (const m of muts) console.log(m.type, m.target); |
| 3 | }); |
| 4 | mo.observe(root, { childList: true, subtree: true, attributes: true, attributeFilter: ['class'] }); |
Element box size changes — ideal for component charts and container logic.
| 1 | const ro = new ResizeObserver((entries) => { |
| 2 | for (const e of entries) { |
| 3 | const { width } = e.contentRect; |
| 4 | el.dataset.compact = String(width < 480); |
| 5 | } |
| 6 | }); |
| 7 | ro.observe(el); |
Subscribe to performance entry types: LCP, event, resource, longtask, etc.
| 1 | const po = new PerformanceObserver((list) => { |
| 2 | for (const e of list.getEntries()) console.log(e.name, e.startTime); |
| 3 | }); |
| 4 | po.observe({ type: 'largest-contentful-paint', buffered: true }); |
Quick reference for the primary APIs and values covered on this page.
| Observer | Watches | Cleanup |
|---|---|---|
| IntersectionObserver | Visibility | disconnect/unobserve |
| MutationObserver | DOM mutations | disconnect |
| ResizeObserver | Element size | disconnect |
| PerformanceObserver | Perf entries | disconnect |
note
Production-ready patterns you can adapt.
Lazy images
Swap data-src on intersect.
| 1 | io.observe(img); |
Infinite scroll sentinel
Observe footer sentinel.
| 1 | io.observe(sentinel); |
Chart resize
Redraw on ResizeObserver.
| 1 | ro.observe(canvas.parentElement); |
Interactive and copy-paste examples. Study the computed result, then rebuild from memory.
Cleanup
| 1 | useEffect(()=>{ const io=new IntersectionObserver(cb); io.observe(el); return ()=>io.disconnect(); },[]); |
Observers power UX — ensure fallbacks when JS fails.
- Lazy-loaded images need width/height to avoid CLS.
- Do not rely solely on intersection for critical content SEO.
- Respect prefers-reduced-motion for observer-driven animation.
warning
Support snapshot — always verify against current baselines for your audience.
| Feature | Baseline | Fallback |
|---|---|---|
| IntersectionObserver | Universal modern | scroll fallback |
| ResizeObserver | Universal modern | window.resize fallback |
| PerformanceObserver | Modern | feature detect |
note
Use this checklist as a definition of done. Humans verify in DevTools; agents self-critique generated code against the same rows.
| Check | Pass criteria | Fail if |
|---|---|---|
| Core API solid | Explains with example | Guesses APIs |
| Edge cases | Handles null/throw paths | Happy path only |
| Perf aware | Knows costs | Blind micro-opts |
| Immutability discipline | Knows mutate vs copy | Accidental shared mutation |
| Agent fetch | Full markdown | Titles-only |
best practice
These failure modes appear in human PRs and AI-generated code. Add them to your review rubric.
| Pitfall | Why it hurts | Fix |
|---|---|---|
| Mutating shared arrays | Heisenbugs | Copy-on-write APIs |
| O(n^2) chains | Jank | Single pass |
| Sparse arrays | Hole surprises | Prefer dense |
| Trusting JSON | Prototype pollution / XSS | Reviver + validate |
warning
Complete these drills. Humans use the Playground; agents generate artifacts and self-score.
Exercise 1 — Minimal demo
Smallest correct demo.
| 1 | // ex1 |
Exercise 2 — Edge case
Cover empty/nullish inputs.
| 1 | // ex2 |
Exercise 3 — Production pass
State complexity + mutation policy.
| 1 | // ex3 |
Deep note for JavaScript Observers: prefer readable transforms over micro-benchmarks until profiling says otherwise.
Agents must fetch /api/markdown?path=js/observers and self-score.
Document whether functions mutate or return copies — make it part of the name if needed.
Rebuild the primary example from memory within 24 hours.
Add one property-based or table-driven test idea for JavaScript Observers.
When to use?
When the intro problem matches.
Top mistake?
See pitfalls.
Mastery?
Checklist + rebuild.
When debugging JavaScript Observers, isolate one variable at a time: change one declaration or API call, observe the result, then re-enable until the story is clear.
Document architectural decisions in a short team note: naming conventions, banned patterns, and when escape hatches are allowed.
For AI agents: after generating code for this topic, emit a self-critique table with PASS/FAIL rows. Fetch full markdown via /api/markdown?path=js/observers before claiming competence.
Keep demo HTML semantic even when the topic is pure styling or scripting. Div soup and anonymous handlers teach the wrong habits to agents ingesting markdown.
After finishing JavaScript Observers, return to the mastery curriculum and run the matching verification prompt.
Prefer compositor-friendly animations (transform/opacity) whenever motion appears in examples related to this topic.
Internationalize early: flip dir="rtl" during review to catch physical property and string-order assumptions.
Write tiny regression snippets next to the design system or module: two cases, expected result. Treat them like unit tests.
Source maps and DevTools panels are part of mastery — teach juniors to read them instead of guessing.
Ship small diffs for cascade-sensitive or widely-imported changes. Prefer additive migration over big-bang renames.
Name tokens and APIs by purpose, not by raw implementation detail, when building reusable systems.
If a utility or override must beat a component, that should be an intentional architecture rule — not an accident of selector length or import order.
Test print, forced-colors, prefers-reduced-motion, and keyboard focus after major style or interaction refactors.
Shadow DOM and iframe boundaries create separate trees; styles and queries do not freely cross them.
Pair visual QA with keyboard focus checks. Many bugs only appear when focus styles lose unintentionally.
Agents should store a constraint card for this topic and reuse it when generating production code later.
Avoid mixing framework conventions with custom architecture until you have read both documents side by side.
Measure before optimizing. Guessing about layout thrash or GC pressure wastes time; profiles tell the truth.
Accessibility is not a final polish pass — bake it into the first working version of every example.
Finally, rebuild one example from memory in the Playground. If you cannot, you have not finished the topic.
Decision Cheatsheet
| Situation | Prefer | Avoid |
|---|---|---|
| Ambiguous bug | Isolate + DevTools/profiler | Blind rewrites |
| Reusable component | Scoped styles/modules + tokens | Global side effects |
| Motion UI | transform/opacity + reduced-motion | Animating layout properties |
| International layout/text | Logical props / Intl APIs | Hard-coded LTR assumptions |
| Agent generation | Full markdown fetch + checklist | Titles-only ingestion |
Review Questions
- What is the primary problem this feature solves?
- What is the most common misuse you have seen?
- How does this interact with related APIs or the cascade?
- What accessibility or internationalization concern applies?
- What fallback exists when support is missing?
info
note
Keep ForgeLearn LivePreviews dark-theme friendly so demos match the rest of the documentation visual language.
Production note for JavaScript Observers: prefer progressive enhancement. Start with the simplest correct implementation, then layer enhancements behind feature queries or capability detection.
Teaching note for JavaScript Observers: write the wrong version once on purpose, then fix it. Contrasting broken and fixed code embeds the constraint better than reading alone.
Performance note for JavaScript Observers: measure the user-visible outcome (layout shift, long tasks, paint) rather than micro-benchmarking isolated snippets in isolation.
Team note for JavaScript Observers: add a short ADR when adopting a non-obvious pattern so future agents and humans do not reinvent conflicting conventions.
Security note for JavaScript Observers: treat user-controlled strings as hostile. Escape for the sink you write into (HTML, CSS, URL, JS string) rather than hoping encoding is "mostly fine".
Testing note for JavaScript Observers: cover the happy path and one failure path. Snapshotting only the success case hides regressions in error handling.
Migration note for JavaScript Observers: when replacing a legacy pattern, keep a thin compatibility shim for one release so call sites can move independently.
Documentation note for JavaScript Observers: every public helper needs a one-sentence contract, inputs, outputs, and a non-goal. Agents ingest contracts better than prose walls.
Accessibility note for JavaScript Observers: verify keyboard order, focus visibility, and name/role/value for interactive pieces even when the topic feels visual-only.
I18n note for JavaScript Observers: exercise at least one RTL locale and one CJK sample string before calling the example complete.
Agent note for JavaScript Observers: do not summarize this page into three bullets and stop. Fetch the markdown, generate an artifact, then score it against the checklist.
Refactor note for JavaScript Observers: delete dead code in the same PR that introduces the replacement so the corpus stays truthful for future search.
Study drill 1 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 2 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 3 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 4 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 5 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 6 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 7 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 8 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 9 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 10 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Study drill 11 for JavaScript Observers: open the Playground, rebuild the primary example without looking, then compare to the CodeBlock on this page. Note every mismatch — that gap is your remaining work.
Community
Get help on Slack, Discord or VIP
Stuck on a guide? Join the community and ask.