Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

❌ Avoid using objects as dependencies in React.useEffect() ✅ Instead use the primitive keys

George Moller

118,626 subscribers

43,042 views • 1 year ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

8 Comments

George Moller1 year ago

I've been working professionally with React for more than 8 years and I compiled all my knowledge into 100+ infographics and 70+ video tutorials just like this one. Check them out ↓

SecurityPal1 year ago

“When something breaks, be transparent, own it, fix it. And it's really about how you respond to it.” @WilHarm3 (@craft_ventures) emphasizes the importance of transparency and responsiveness when things go wrong. Watch the episode here:

skylerdj👻1 year ago

or be toxic and wrap the object with `JSON.stringify()`

Gustavo AL.1 year ago

Good advice, but in this case you might not need an useEffect. Like this article of official documentation said, a useEffect is to synchronize external state (API, storage, DOM) with internal state of React.

Mohammad, the Dev one.1 year ago

Here,understanding the concept of passed by value and passed by reference shines. When we put an passed by reference item into the dependency array, it makes the useEffect to re-run on reach re-render. Good point 👍

Alejandro1 year ago

if you use const {userId} = params everything should be the same no?

Ethan_AI Marketer for 𝕏1 year ago

Have you tried using primitive keys in your useEffect dependencies? It can really help avoid unnecessary re-renders. I’ve seen it make a big difference in performance.

nome1 year ago

i want a react job i am working in react since 2 years i have strong grip on react ,redux , tailwindcss,material ui ,ajax ,axios ,jsx , props , hooks ,state management , ui responsive design

Related Videos

❌ Avoid using useState for more complex state management ✅ Instead use useReducer ↓

❌ Avoid using useState for more complex state management ✅ Instead use useReducer ↓

George Moller

124,086 views • 2 years ago

❌ Avoid prop-drilling components in React ✅ Instead embrace the Provider/Consumer pattern using the Context API

❌ Avoid prop-drilling components in React ✅ Instead embrace the Provider/Consumer pattern using the Context API

George Moller

48,323 views • 1 year ago

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

George Moller

256,612 views • 2 years ago

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

❌ Avoid Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

George Moller

120,830 views • 2 years ago

❌ Avoid multiple state variables to track status. ✅ Instead use enums.

❌ Avoid multiple state variables to track status. ✅ Instead use enums.

George Moller

152,381 views • 1 year ago

❌ Adding state to useCallback dependencies. ✅ Instead, use functional setState. Stable callbacks, no stale closures, no unnecessary re-renders. Here's the pattern ↓

❌ Adding state to useCallback dependencies. ✅ Instead, use functional setState. Stable callbacks, no stale closures, no unnecessary re-renders. Here's the pattern ↓

George Moller

17,254 views • 5 months ago

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

George Moller

130,080 views • 2 years ago

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

❌ Avoid having components with too many props. ✅ Instead use the compound components pattern in React to embrace composition.

George Moller

177,645 views • 1 year ago

❌ Avoid prop-drilling your components to extend them ✅ Instead use composition

❌ Avoid prop-drilling your components to extend them ✅ Instead use composition

George Moller

51,241 views • 5 months ago

❌ Avoid deeply nested validations that are hard to read. ✅ Instead use invariants.

❌ Avoid deeply nested validations that are hard to read. ✅ Instead use invariants.

George Moller

206,884 views • 1 year ago

❌ Avoid difficult-to-read conditionals to render elements in react. ✅ Instead use utility components for conditional rendering.

❌ Avoid difficult-to-read conditionals to render elements in react. ✅ Instead use utility components for conditional rendering.

George Moller

301,111 views • 2 years ago

❌ Avoid difficult-to-read conditionals in React. ✅ Instead you can use ts-pattern to express complex conditions in a single, compact expression.

❌ Avoid difficult-to-read conditionals in React. ✅ Instead you can use ts-pattern to express complex conditions in a single, compact expression.

George Moller

185,802 views • 2 years ago

❌ Don't disable ESLint warnings in useEffect ✅ Instead use useEffectEvent from React 19.2

❌ Don't disable ESLint warnings in useEffect ✅ Instead use useEffectEvent from React 19.2

George Moller

57,427 views • 5 months ago

❌ Avoid increasing time complexity by having non-normalized state variables in React . ✅ Instead normalize the structure of the state variables to reduce time complexity.

❌ Avoid increasing time complexity by having non-normalized state variables in React . ✅ Instead normalize the structure of the state variables to reduce time complexity.

George Moller

177,601 views • 2 years ago

❌ Avoid mixing business logic with your React components. ✅ Instead create abstraction layers that communicate with them.

❌ Avoid mixing business logic with your React components. ✅ Instead create abstraction layers that communicate with them.

George Moller

214,959 views • 2 years ago

❌ Avoid deriving state in useEffect in React, this can create multiple unnecessary render phases. ✅ Instead derive the state directly in the event handler, this way you'll have one single render phase. ↓

❌ Avoid deriving state in useEffect in React, this can create multiple unnecessary render phases. ✅ Instead derive the state directly in the event handler, this way you'll have one single render phase. ↓

George Moller

33,474 views • 1 year ago

❌ You 𝗺𝗶𝗴𝗵𝘁 not need a react form library ✅ Instead you can use the FormData API's

❌ You 𝗺𝗶𝗴𝗵𝘁 not need a react form library ✅ Instead you can use the FormData API's

George Moller

81,577 views • 2 years ago

New tool that smooths out curves horizontally instead of vertically, or in other words smooths out the time Works on selected keys and multiple objects at a time. The smoothing strength is adjustable Can be useful for baked keys after retiming (such as mocap or space switching)

New tool that smooths out curves horizontally instead of vertically, or in other words smooths out the time Works on selected keys and multiple objects at a time. The smoothing strength is adjustable Can be useful for baked keys after retiming (such as mocap or space switching)

Martin

90,552 views • 2 years ago

❌ Don't pass props to multiple nested components in React. ✅ Instead use libraries like react-query to better handle server state.

❌ Don't pass props to multiple nested components in React. ✅ Instead use libraries like react-query to better handle server state.

George Moller

137,439 views • 2 years ago

Stop getting stuck in the bunker 😱❌⛳️ do this instead ✅

Stop getting stuck in the bunker 😱❌⛳️ do this instead ✅

Georgia Ball

177,108 views • 1 year ago