Frontend Mastery

Effective useState & useEffect: Avoiding infinite loops

1 Views Updated 5/4/2026

State & Effects Mastery

Hooks are the power of React, but they are also the most common source of bugs. useState manages data, and useEffect manages Side Effects (API calls, subscriptions). If you don't understand the "Dependency Array," you will crash your browser.

1. The Dependency Array Rule

The second argument to useEffect tells React when to run the effect.

  • No Array: Runs on EVERY render. (Extremely dangerous).
  • Empty Array []: Runs only once on Mount. (Perfect for initial API calls).
  • [data]: Runs only when 'data' changes.

2. The Infinite Loop Trap

If you call setData() inside a useEffect that has 'data' in its dependency array, you create a loop: Effect -> State Change -> Re-render -> Effect -> State Change... until the tab crashes.

3. Cleanup Functions

Always return a cleanup function to prevent Memory Leaks. If you set a setInterval or a WebSocket, you must clear it when the component unmounts.

4. Interview Mastery

Q: "What is the difference between useEffect and useLayoutEffect?"

Architect Answer: "`useEffect` runs *asynchronously* after the render is painted on the screen. It is non-blocking. `useLayoutEffect` runs *synchronously* after all DOM mutations but *before* the browser paints. You should use `useLayoutEffect` only when you need to measure DOM elements (like a tooltip position) and update them before the user sees a 'flicker'."

Frontend Mastery
1. Core Foundation & Modern JS
ES6+ for Architects: Closures, Generators, and Symbols Asynchronous JS: Event Loop, Microtasks, and Promises TypeScript Mastery: Advanced Types, Generics, and Utility Types
2. React Internals & Core Hooks
Virtual DOM vs Reconciliation: The Fiber Architecture Effective useState & useEffect: Avoiding infinite loops useMemo vs useCallback: When optimization becomes a bottleneck useContext + useReducer: Building a built-in state manager Custom Hooks: Extracting business logic for reusability
3. Professional State Management
Redux Toolkit (RTK): Slices, Selectors, and Thunks RTK Query: Automating API caching and synchronization Zustand: The lightweight alternative to Redux Signal-based State: The future of fine-grained reactivity
4. Performance & Rendering
Component Re-rendering: How to profile and fix slow UIs Lazy Loading & Code Splitting: Shrinking your bundle size Virtualization: Rendering million-row lists efficiently Web Workers: Offloading heavy calculations to background threads
5. Design Systems & CSS
Modern CSS: Grid, Flexbox, and Container Queries CSS-in-JS vs TailWindCSS: Choosing the right styling strategy Storybook: Building a shared component library Accessibility (a11y): Building inclusive web interfaces
6. Next.js & Modern Frameworks
Next.js App Router: SSR vs SSG vs ISR React Server Components (RSC): The end of the Waterfall Data Fetching Patterns: Streaming and Suspense SEO for Frontend: Meta Tags, JSON-LD, and Core Web Vitals
7. Testing & Security
Unit Testing: Vitest and React Testing Library E2E Testing: Playwright for mission-critical flows Frontend Security: XSS, CSRF, and Content Security Policy State Synchronization: Optimistic UI & WebSockets
8. Final Polish & Interview
Micro-Frontends: Scalable architecture for enterprise teams Frontend Architect Interview: System Design & Performance