Yeah, there are several issues asking us to be more aggressive about either recognizing code as unreachable or issuing errors when we already do (like here—`value` is successfully narrowed to `never` inside `if (!value)`, but the user has no way of noticing that because they think they just detected it to be `undefined`, so of course they’re not going to try to use it). But I like this issue because the scope is very narrow, and seems to sit well within the unawaited Promise / uncalled function checks we already have.
Also related is #45267