--- title: Goodbye useEffect: Exploring use() in React 19 : fireup.pro description: React 19 introduces the use() hook, transforming asynchronous operations in React applications. By addressing issues inherent to useEffect, use() simplifies... canonical: https://daily.dev/posts/n3ctqinla twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Goodbye useEffect: Exploring use() in React 19 : fireup.pro | daily.dev og:description: React 19 introduces the use() hook, transforming asynchronous operations in React applications. By addressing issues inherent to useEffect, use() simplifies... og:url: https://daily.dev/posts/n3ctqinla og:image: https://api.daily.dev/og/posts/N3cTqINLa.png og:image:alt: Post cover image og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Goodbye useEffect: Exploring use() in React 19 : fireup.pro **[WebDev](https://daily.dev/sources/webdev)** · [@krystianjj](https://daily.dev/krystianjj) · 347 upvotes · 24 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Community discussion Top comments from developers on daily.dev. **@earthjan** · 13 upvotes > Isn't that `useEffect` has its own use case, allowing your components to react to side effects? If so, introducing a mindset that `useEffect` should be the last thing to think of isn't right. > > **How to manage side effects by React**: https://react.dev/learn/synchronizing-with-effects > > **How not to use useEffect:** https://react.dev/learn/you-might-not-need-an-effect#caching-expensive-calculations **@friedrich** · 9 upvotes > But you will still need useEffect for side effects, right 😅 ? **@bthe125** · 5 upvotes > This article is incorrect in how it's framing the new `use` feature. It is not a hook, it is an API. Though a case can be made for how it can be used instead of `useEffect`, it's not technically a direct replacement for `useEffect` and `useEffect` will still have it's own usecases. Read more here https://react.dev/reference/react/use **@knight\_03** · 4 upvotes > Much needed thing for react!!! **@dylansacco** · 2 upvotes > This is a great change ## Similar posts on daily.dev - [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 1 upvotes · 0 comments - [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments - [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments - [CNCF Unveils Schedule for KubeCon \+ CloudNativeCon Europe 2026](https://daily.dev/posts/cncf-unveils-schedule-for-kubecon-cloudnativecon-europe-2026-ikhcoa5cb) · CNCF · 2 upvotes · 0 comments - [CNCF Debuts KubeCon \+ CloudNativeCon Japan 2026 Schedule](https://daily.dev/posts/cncf-debuts-kubecon-cloudnativecon-japan-2026-schedule-xp5pyudub) · CNCF · 1 upvotes · 0 comments --- Tags: [#webdev](https://daily.dev/tags/webdev), [#javascript](https://daily.dev/tags/javascript), [#react](https://daily.dev/tags/react), [#react-hooks](https://daily.dev/tags/react-hooks) [View this post on daily.dev](https://daily.dev/posts/n3ctqinla) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"DiscussionForumPosting","mainEntityOfPage":"https://daily.dev/posts/n3ctqinla","headline":"Goodbye useEffect: Exploring use() in React 19 : fireup.pro","text":"Shared: Goodbye useEffect: Exploring use() in React 19 : fireup.pro","url":"https://daily.dev/posts/n3ctqinla","datePublished":"2025-05-21T05:11:26.657Z","dateModified":"2025-05-21T05:11:26.660Z","author":{"@type":"Person","name":"Krystian","url":"https://daily.dev/krystianjj","image":"https://media.daily.dev/image/upload/s--czhurieh--/f_auto/v1739726913/avatars/avatar_KNBb5vqfx0qafJYg8dfPX","description":"Software Engineer focused on Web Performance & UX","worksFor":{"@type":"Organization","name":"fireup.pro","logo":"https://res.cloudinary.com/daily-now/image/upload/s--zt6bZfJq--/f_auto/v1727857350/companies/fireup"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"EndorseAction"},"userInteractionCount":320}},"image":"https://media.daily.dev/image/upload/s--HRgLpUt6--/f_auto/v1722860399/public/Placeholder%2003","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":347},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":24}],"sharedContent":{"@type":"WebPage","url":"https://api.daily.dev/r/6QzwIZQ5T"},"comment":[{"@type":"Comment","text":"Isn’t that useEffect has its own use case, allowing your components to react to side effects? If so, introducing a mindset that useEffect should be the last thing to think of isn’t right.\nHow to manage side effects by React: https://react.dev/learn/synchronizing-with-effects\nHow not to use useEffect: https://react.dev/learn/you-might-not-need-an-effect#caching-expensive-calculations","datePublished":"2025-05-26T11:11:07.353Z","dateModified":"2025-05-26T11:12:35.494Z","url":"https://daily.dev/posts/N3cTqINLa#c-MFk6cwtt1","author":{"@type":"Person","name":"Earth Jan Baquir Marzan","url":"https://daily.dev/earthjan"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":13}},{"@type":"Comment","text":"But you will still need useEffect for side effects, right 😅 ?","datePublished":"2025-05-21T10:15:30.992Z","url":"https://daily.dev/posts/N3cTqINLa#c-5LswV79JZ","author":{"@type":"Person","name":"Friedrich WT","url":"https://daily.dev/friedrich","image":"https://avatars.githubusercontent.com/u/136119888?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":9}},{"@type":"Comment","text":"This article is incorrect in how it’s framing the new use feature. It is not a hook, it is an API. Though a case can be made for how it can be used instead of useEffect, it’s not technically a direct replacement for useEffect and useEffect will still have it’s own usecases. Read more here https://react.dev/reference/react/use","datePublished":"2025-05-29T04:16:45.913Z","dateModified":"2025-06-04T15:16:24.885Z","url":"https://daily.dev/posts/N3cTqINLa#c-xJp06uLbe","author":{"@type":"Person","name":"Byron","url":"https://daily.dev/bthe125","image":"https://lh3.googleusercontent.com/a/ALm5wu3CH6FdKSdVEySyYUC86vLTl0z7C52kwbw-jbugZA=s96-c"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":5}},{"@type":"Comment","text":"Much needed thing for react!!!","datePublished":"2025-05-21T06:51:36.900Z","url":"https://daily.dev/posts/N3cTqINLa#c-IgjBUn7a9","author":{"@type":"Person","name":"Dhvani","url":"https://daily.dev/knight_03","image":"https://media.daily.dev/image/upload/s--h8XDcpiq--/f_auto/v1740025441/avatars/avatar_xWOJioMgO9tVQ6TcQUdqZ"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":4}},{"@type":"Comment","text":"This is a great change","datePublished":"2025-06-05T13:23:38.435Z","url":"https://daily.dev/posts/N3cTqINLa#c-2pSpBtEA3","author":{"@type":"Person","name":"Dylan Sacco","url":"https://daily.dev/dylansacco","image":"https://avatars.githubusercontent.com/u/115655789?v=4"},"interactionStatistic":{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2}}],"isPartOf":{"@type":"WebPage","url":"https://daily.dev/squads/webdev","name":"WebDev"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"WebDev","item":"https://daily.dev/squads/webdev"},{"@type":"ListItem","position":3,"name":"Goodbye useEffect: Exploring use() in React 19 : fireup.pro"}]} ```