Pending Promises sent from server to client component crash if they reject without a reason about next.js

[edspencer]

Slightly more context: it looks like calling reject() without a reason is supported when the promise is on the client side - see https://react.dev/reference/react/use#dealing-with-rejected-promises

I'm guessing that this may be something to do with how Flight deals with promise resolution.

[little077]

.catch(e=>{
return "no new message found.";
});Maybe you need to throw a catch to catch him

[edspencer]

.catch(e=>{ return "no new message found."; });Maybe you need to throw a catch to catch him

Yes, you can write that code, but it's non-obvious that you need to, and if the Promise that rejects is not in your own codebase then it may be difficult/impossible to do that. Also, it's not going to trigger your error boundary, so now you have 2 code paths to handle errors.

I think this is a bug as it doesn't seem reasonable that rejecting a promise without an argument (which is a valid use of reject()) should crash the process and halt the response. There are workarounds - the catch you mention and also passing an Error instance to reject() (you can even just call reject({digest: 'something'}) as it's the .digest property the code is looking for), but I lost of few hours of my life figuring this out and I can see it affecting others too.