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 Provider wrapping hell in React. ✅ Instead combine all your Providers using composition.

George Moller

118,888 subscribers

120,830 views • 2 years ago •via X (Twitter)

Education Science & Technology

Anya Rossi• Live Now

Private livecam show

10 Comments

George Moller2 years 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 ↓

Stephen Burke2 years ago

This seems like a useless abstraction. You typically never need to touch that nest so adding all of that extra code to achieve the same result seems pointless. What am I missing?

Sarju2 years ago

By doing this you are increasing lines of code, complexity and bug surface area and reducing readability and plus if you are using typescript, there will be lots of extra things to handle compare to original one.

Farley2 years ago

What are you closing exactly?

Paulo Barros2 years ago

@fernandozabin @feokuma @AmorimRob

Chung Wei2 years ago

This makes your code even harder to read and maintain, not to mention an unnecessary loop. Just move all providers into a separate component and call it a day.

احمد الشبيب2 years ago

Love your tips George, but this one is not for me. Regardless of the unreadable code I had to create for our lord Typescript, but the App initial start seems to have an odd behavior now? It looks like its re-loading multiple times before it actually settles. Before and After 👇

Anthony Laflamme2 years ago

Clever

allen.xyz2 years ago

Does this require order to be maintained in the array?

MMILife2 years ago

What's the pros and cons aside from readability?

Related Videos

❌ 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,599 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,311 views • 1 year 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,627 views • 1 year 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,061 views • 2 years 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

50,727 views • 4 months 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,951 views • 2 years ago

❌ 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,069 views • 2 years 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

❌ 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,237 views • 4 months 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

❌ 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,429 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,253 views • 1 year 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,841 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

❌ Conditional rendering loses form state in React. ✅ React 19's Activity API preserves it. e.g. Switch between steps → your data stays. Effects cleanup automatically → no wasted resources.

❌ Conditional rendering loses form state in React. ✅ React 19's Activity API preserves it. e.g. Switch between steps → your data stays. Effects cleanup automatically → no wasted resources.

George Moller

74,003 views • 5 months ago

Dear Muslims, avoid using these words in your homes...

Dear Muslims, avoid using these words in your homes...

Idris

19,914 views • 1 year ago

5 Cursor beginner mistakes to avoid: 1. Using AI pane instead of Composer 2. Not saving your project enough 3. Not including all files as context (and using mention) 4. Doing too many changes at once 5. Using Cursor for UI, instead of v0 Video to walk you through it ⬇️

5 Cursor beginner mistakes to avoid: 1. Using AI pane instead of Composer 2. Not saving your project enough 3. Not including all files as context (and using mention) 4. Doing too many changes at once 5. Using Cursor for UI, instead of v0 Video to walk you through it ⬇️

Moritz Kremb

206,374 views • 1 year ago

All natural gardening tip to unalive weeds! 😉 Avoid using toxic chemicals in and around your home by making the switch.

All natural gardening tip to unalive weeds! 😉 Avoid using toxic chemicals in and around your home by making the switch.

Shawnee Gregorio

62,590 views • 1 month ago

What a day at the Rivals Combine in Nashville. Completely sold out, verified combine times and data for all athletes in attendance 🔥 Rivals High School ✅ 1,700+ athletes ✅ 41 states represented Largest event we’ve ever run. Earn your stars 💯

What a day at the Rivals Combine in Nashville. Completely sold out, verified combine times and data for all athletes in attendance 🔥 Rivals High School ✅ 1,700+ athletes ✅ 41 states represented Largest event we’ve ever run. Earn your stars 💯

Billy Tucker

18,908 views • 1 month ago

❌ useMemo, useCallback, memo everywhere ✅ React Compiler handles it automatically React Compiler v1.0 is here. It analyzes your code at build time and adds memoization where needed.↓

❌ useMemo, useCallback, memo everywhere ✅ React Compiler handles it automatically React Compiler v1.0 is here. It analyzes your code at build time and adds memoization where needed.↓

George Moller

62,751 views • 4 months ago