Is React 18 double calling useEffects a mistake, or a sign of an awesome feature that will help you build more reliable components? Let's find out!
Strict Mode documentation: [ Ссылка ]
👉 Practical Module Federation Book: [ Ссылка ]
👉 No BS TS (The Book): [ Ссылка ]
👉 I'm a host on the React Round-Up podcast: [ Ссылка ]
👉 Don't forget to subscribe to this channel for more updates: [ Ссылка ]
👉 Discord server signup: [ Ссылка ]
👉 VS Code theme and font? Night Wolf [black] and Operator Mono
👉 Terminal Theme and font? oh-my-posh with powerlevel10k_rainbow and SpaceMono NF
0:00 Introduction
1:10 Example Setup
3:32 The (Not) Problem
5:04 What Strict Mode Covers?
6:24 The (Not) Fix
7:56 Migrate Heavyweights Off Of useEffect
8:40 Is It A Good Developer Experience?
10:14 Outroduction
#reactjs #react18 #react_useEffect
React 18: useEffect Double Call; Mistake or Awesome?
Теги
React 18 useEffectjack herrington useEffectreact 18 strict modeReact 18: useEffect + Strict Modeblue collar coderuseEffect double renderreact 18react 18 useeffectreact 18 use effect double calluse effect double callreact strict modeuseEffect + Strict ModeReact 18useeffect multiple triggersuseeffect multiple api callsuseeffect double renderuseeffect react 18jack herrington
