aa489c7eb8
Add detailed landing page development plan in docs/frontend_landing_plan.md: - Complete landing page structure (Hero, Problem/Solution, Features, Demo, CTA) - Design guidelines from downloaded skills (typography, color, motion, composition) - Security considerations (XSS prevention, input sanitization, CSP) - Performance targets (LCP <2.5s, bundle <150KB, Lighthouse >90) - Responsiveness and accessibility requirements (WCAG 2.1 AA) - Success KPIs and monitoring setup - 3-week development timeline with daily tasks - Definition of Done checklist Download 10+ frontend/UI/UX skills via universal-skills-manager: - frontend-ui-ux: UI/UX design without mockups - frontend-design-guidelines: Production-grade interface guidelines - frontend-developer: React best practices (40+ rules) - frontend-engineer: Next.js 14 App Router patterns - ui-ux-master: Comprehensive design systems and accessibility - ui-ux-systems-designer: Information architecture and interaction - ui-ux-design-user-experience: Platform-specific guidelines - Plus additional reference materials and validation scripts Configure universal-skills MCP with SkillsMP API key for curated skill access. Safety first: All skills validated before installation, no project code modified. Refs: Universal Skills Manager (github:jacob-bd/universal-skills-manager) Next: Begin Sprint 3 landing page development
56 lines
1.4 KiB
Markdown
56 lines
1.4 KiB
Markdown
---
|
|
title: Store Event Handlers in Refs
|
|
impact: LOW
|
|
impactDescription: stable subscriptions
|
|
tags: advanced, hooks, refs, event-handlers, optimization
|
|
---
|
|
|
|
## Store Event Handlers in Refs
|
|
|
|
Store callbacks in refs when used in effects that shouldn't re-subscribe on callback changes.
|
|
|
|
**Incorrect (re-subscribes on every render):**
|
|
|
|
```tsx
|
|
function useWindowEvent(event: string, handler: () => void) {
|
|
useEffect(() => {
|
|
window.addEventListener(event, handler)
|
|
return () => window.removeEventListener(event, handler)
|
|
}, [event, handler])
|
|
}
|
|
```
|
|
|
|
**Correct (stable subscription):**
|
|
|
|
```tsx
|
|
function useWindowEvent(event: string, handler: () => void) {
|
|
const handlerRef = useRef(handler)
|
|
useEffect(() => {
|
|
handlerRef.current = handler
|
|
}, [handler])
|
|
|
|
useEffect(() => {
|
|
const listener = () => handlerRef.current()
|
|
window.addEventListener(event, listener)
|
|
return () => window.removeEventListener(event, listener)
|
|
}, [event])
|
|
}
|
|
```
|
|
|
|
**Alternative: use `useEffectEvent` if you're on latest React:**
|
|
|
|
```tsx
|
|
import { useEffectEvent } from 'react'
|
|
|
|
function useWindowEvent(event: string, handler: () => void) {
|
|
const onEvent = useEffectEvent(handler)
|
|
|
|
useEffect(() => {
|
|
window.addEventListener(event, onEvent)
|
|
return () => window.removeEventListener(event, onEvent)
|
|
}, [event])
|
|
}
|
|
```
|
|
|
|
`useEffectEvent` provides a cleaner API for the same pattern: it creates a stable function reference that always calls the latest version of the handler.
|