unknown

React 19 introduces the use() hook, transforming asynchronous operations in React applications. By addressing issues inherent to useEffect, use() simplifies state management, improves testing, and reduces boilerplate code. It works alongside Suspense to manage promise handling, enabling declarative data dependencies and progressive UI rendering.

Goodbye useEffect: Exploring use() in React 19 : fireup.pro

The official daily.dev web development community. Led by thought leaders and webdev experts. Join the Squad!

WebDev

Isn’t that <code>useEffect</code> has its own use case, allowing your components to react to side effects? If so, introducing a mindset that <code>useEffect</code> should be the last thing to think of isn’t right.
How to manage side effects by React: <a href="https://react.dev/learn/synchronizing-with-effects" target="_blank" rel="noopener nofollow">https://react.dev/learn/synchronizing-with-effects</a>
How not to use useEffect: <a href="https://react.dev/learn/you-might-not-need-an-effect#caching-expensive-calculations" target="_blank" rel="noopener nofollow">https://react.dev/learn/you-might-not-need-an-effect#caching-expensive-calculations</a>

But you will still need useEffect for side effects, right 😅 ?

This article is incorrect in how it’s framing the new <code>use</code> feature. It is not a hook, it is an API. Though a case can be made for how it can be used instead of <code>useEffect</code>, it’s not technically a direct replacement for <code>useEffect</code> and <code>useEffect</code> will still have it’s own usecases. Read more here <a href="https://react.dev/reference/react/use" target="_blank" rel="noopener nofollow">https://react.dev/reference/react/use</a>