In this post, I’ll demo how to read a value from a promise using use.
Demo
Codebase
Let’s check out the following code:
import { Suspense } from "react"; export default function Page() { const messagePromise = fetchMessages(); return ( <Suspense fallback={<p>⌛ waiting for messages...</p>}> <Message messagePromise={messagePromise} /> </Suspense> ); }
A couple of things to note:
messagePromise is a promise passed as a prop to
Now, let’s take a look at fetchMessages:
async function fetchMessages() { return [ { id: 1, text: "message 1", }, { id: 2, text: "message 2", }, ]; }
As you can see, it’s a very simple function. In a real world example, this could be a fetch request, but for simplicity, the function just returns an array. By using async, JavaScript automatically knows that the function returns a promise.
Finally, let’s check out the
function Message({ messagePromise }) { const comments = use(messagePromise); return comments.map((comment) => <p key={comment.id}>{comment.text}</p>); }
This is where it gets interesting. The
Usually, you’d use await with a promise, but in React 19, you can now use use to achieve basically the same result.
One key difference between await and use is that await blocks rendering until the promise is resolved, whereas use doesn’t block rendering.
Here’s how the component looks before the promise is resolved:
And once the promise is resolved:
use works similarly to await, and if the application is running on a server using SSR, the result is exactly the same: the server will return the same HTML response in both cases.
However, if the code runs on the client, rendering behaves a bit differently. await blocks rendering until the promise is resolved, while use allows the component to re-render once the promise is resolved.
The above is the detailed content of React New API use(promise). For more information, please follow other related articles on the PHP Chinese website!