<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section! Please help us by doing the following steps before logging an issue: * Search: https://github.com/Microsoft/TypeScript/search?type=Issues * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ Please fill in the *entire* template below. --> <!-- Please try to reproduce the issue with the latest published version. It may have already been fixed. For npm: `typescript@next` This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly --> **TypeScript Version:** Nightly <!-- Search terms you tried before logging this (so others can find this issue more easily) --> **Search Terms:** `undefined`, `destructure`, `destructuring` **Code** ```ts interface Foo { foo1: string } let foo: Foo | undefined; const { foo1 } = foo; // foo1: string ``` **Expected behavior:** As in 3.8, the `const { foo1 } = foo;` should emit error `Property 'foo1' does not exist on type 'Foo | undefined'.(2339)` **Actual behavior:** No error emitted. Type of `foo1` is inferred as `string`. **Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior --> https://www.typescriptlang.org/play/?ts=Nightly#code/JYOwLgpgTgZghgYwgAgGIHt3IN4ChnIyYCMAXMgM5hSgDmuAvrrgDYRiGbkZYA+yAVxAATCDFARhAblwJ0IKjk7piyBsgC8yqcgD0u5WUrU6QA **Related Issues:** <!-- Did you find other bugs that looked similar? --> None found