https://peertube.lagbag.com/videos/watch/bf6a8581-5e78-4bae-a9f1-e5e0f5260457 React 18 includes concurrent rendering which might render a useEffect multiple times. If you rely on useEffect for onComponentDidMount, you might have to change that soon. Let's see how React 18 breaks this behaviour in this release and what it means for you. ⚛️ Do you want to become a full-stack web developer? Check out codedamn's full-stack learning path: https://cdm.sh/fullstack ⚛️ Get started with web3 and decentralised technologies today: https://cdm.sh/web3 Timestamps 0:00 Teaser 0:26 useEffect() before React 18 1:15 useEffect() after React 18 2:45 New useEvent() hook 4:48 Why this is happening? 6:30 Conclusion 7:52 Outro 👉 Checkout codedamn on social: Instagram: https://cdm.sh/ig Twitter: https://cdm.sh/twt Discord community: https://cdm.sh/discord Facebook: https://cdm.sh/fb GitHub: https://cdm.sh/github If you found the video valuable, please leave a like and subscribe ❤️ It helps the channel grow and helps me pump out more such content. ✨ Video Tags ✨ React 18 has a HUGE mistake and it's about to break a LOT of code React 18 breaking changes React 18 useEffect rendering twice You Don't Have To Be A Tech Geek to Spot This Bug React 18: The new version that's broken React 18 is broken in a weird way - What is going on? ✨ Hashtags ✨ #react #useEffect react suspense Thu, 09 Apr 2026 20:52:02 GMT https://validator.w3.org/feed/docs/rss2.html PeerTube - https://peertube.lagbag.com https://peertube.lagbag.com/client/assets/images/icons/icon-512x512.png https://peertube.lagbag.com/videos/watch/bf6a8581-5e78-4bae-a9f1-e5e0f5260457 All rights reserved, unless otherwise specified in the terms specified at https://peertube.lagbag.com/about and potential licenses granted by each content's rightholder.