Destructuring a possibly `undefined` object not caught, throws an error at runtime

🔎 Search Terms

destructuring, Cannot destructure as it is undefined, optional chaining destructuring

🕗 Version & Regression Information

• This changed between versions ______ and _______
• This changed in commit or PR _______
• This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________
• I was unable to test this on prior versions because _______

⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.6.2#code/MYewdgzgLgBAlmADgVygLhgbwLACgYEwCGA-BpjAEZlYzAbQBOCA5jAL4d6cC8tRGZGAAmAUwBmCUcK648oSLAoA6VZQ4w+CFFGWlllIA

💻 Code

const input: {
    a?: { b?: { c: string } }
} = { a: undefined }

const { ...b } = input.a?.b

🙁 Actual behavior

No error reported by TypeScript.

🙂 Expected behavior

TypeScript should have an indicative error, since this expression might result in undefined, which cannot be destructured.

Similar to this:

Rest types may only be created from object types.(2700)

Additional information about the issue

The error in the JavaScript being ran is:

Uncaught TypeError: Cannot destructure '(intermediate value)' as it is undefined.

Inizia dal link al Playground di TypeScript 5.6.2 e dall’esempio di destructuring che coinvolge input.a?.b. Traccia come il checker gestisce un oggetto che potrebbe essere undefined in un’espressione di object-rest destructuring, quindi verifica che il comportamento completato riporti un diagnostic indicativo invece di consentire codice che genera un errore a runtime.