
ALT eps1lon: We've discussed this and we don't want to allow async functions at the type level. We're probably going to start warning at runtime when you return a Promise from an event handler. We didn't used to warn because we didn't have a good alternative. With React 19 we have: Use an Action or wrap the async function in startTransition. We may start automatically wrapping async functions in startTransition. But with any additive API this comes with the risk of breaking existing usages that relied on existing behavior even though it was never supported. So by officially allowing them now (even though it "just works"), we increase the risk of not being able to make that change because too much of the ecosystem relied on this behavior. As an escape hatch, you can always wrap the async function in an IIFE or use promise.then(). This makes it more obvious that something after the Promise resolved is outside of React's control.





















