Skip to content
  • Home
  • About
  • No Access
  • Privacy Policy
Bits of .NET
Bits of .NET
  • Asp.Net Core
  • C#
  • SQL
  • JavaScript
  • CSS
  • About
  • ErcanOPAK.com
  • No Access
  • Privacy Policy

Bits of .NET

Daily micro-tips for C#, SQL, performance, and scalable backend engineering.

  • Asp.Net Core
  • C#
  • SQL
  • JavaScript
  • CSS
  • About
  • ErcanOPAK.com
  • No Access
  • Privacy Policy
JavaScript

JavaScript: Why Destructuring a Nested Property Throws Instead of Returning Undefined

- 06.09.26 - ErcanOPAK

⚡ Destructuring a Nested Property Throws an Error Instead of Just Returning Undefined

Accessing a deeply nested property that doesn’t exist normally just returns `undefined` in JavaScript – but destructuring the same nested path throws a `TypeError: Cannot destructure property ‘x’ of ‘undefined’ as it is undefined` instead, because destructuring has to actually READ each intermediate level to pull values out of it, and reading a property OFF of `undefined` is where the error comes from – not the final missing property itself.

🔎 The Problem

const response = { data: null };

const { data: { user } } = response;
// TypeError: Cannot destructure property '"'"'user'"'"' of '"'"'response.data'"'"'
// as it is null.

// Compare to plain property access, which does NOT throw:
const user2 = response.data?.user;   // undefined, no error - if optional
                                       // chaining is used
const user3 = response.data.user;    // ALSO throws here, for the same
                                       // reason - reading .user off null
                                       // fails regardless of destructuring

✅ Fix: Default Values or Optional Chaining, at the Right Level

  • Give the intermediate level a default value directly in the destructuring pattern: `const { data: { user } = {} } = response;` – the `= {}` provides a fallback specifically for when `data` itself is `null`/`undefined`, letting the destructuring of `user` proceed safely against an empty object instead.
  • For deeper or more variable nesting, plain optional chaining before destructuring is often clearer: `const user = response.data?.user;` – it reads more explicitly as “this path might not exist” than a nested destructuring default does.

⚠️ The Rule to Remember

  • The error isn’t really about destructuring specifically – it’s the same “cannot read property of null/undefined” error JavaScript always throws for that access pattern; destructuring just makes it easier to trigger accidentally, since the intermediate access is implicit rather than an explicit `.` you’d naturally think to guard.
  • Destructuring defaults (`= {}`) only kick in when the value is exactly `undefined` – NOT for `null`. A field that’s explicitly `null` (common for “intentionally empty” API responses) still needs its own explicit handling, since `= {}` alone won’t catch it.

Destructuring doesn’t create a new way to fail – it just makes the same ‘reading a property off nothing’ failure easier to trigger without noticing.

— JavaScript Tip

Related posts:

JavaScript Event Listeners Multiply Silently

JavaScript Event Listeners Multiply Silently

Smart way to truncate long strings in Javascript

Smart way to truncate long strings in Javascript

JavaScript: Why a Set Still Contains 'Duplicate' Values That Look Completely Identical

JavaScript: Why a Set Still Contains 'Duplicate' Values That Look Completely Identical

Views: 11

Post navigation

C#: Fix a Recursive Async Method That Grows the Call Stack Until It Crashes
C#: Why a Yield Return Iterator Doesn’t Run Any Code Until You Start Enumerating It

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

November 2026
M T W T F S S
 1
2345678
9101112131415
16171819202122
23242526272829
30  
« Oct    

Most Viewed Posts

  • How to make theater mode the default for Youtube (1,055)
  • Get the User Name and Domain Name from an Email Address in SQL (981)
  • How to add default value for Entity Framework migrations for DateTime and Bool (977)
  • Get the First and Last Word from a String or Sentence in SQL (858)
  • How to select distinct rows in a datatable in C# (854)
  • How to enable, disable and check if Service Broker is enabled on a database in SQL Server (653)
  • Add Constraint to SQL Table to ensure email contains @ (609)
  • Average of all values in a column that are not zero in SQL (570)
  • How to use Map Mode for Vertical Scroll Mode in Visual Studio (547)
  • Find numbers with more than two decimal places in SQL (475)

Recent Posts

  • C#: Fix a ConditionalWeakTable Entry Vanishing Too Soon
  • Docker: Fix a Stale COPY Layer After Editing .dockerignore
  • Photoshop: Fix a Pattern Overlay Scaling Wrong on a High-DPI File
  • SQL Server: Fix a Computed Column Index Skipped by Implicit Cast
  • HTML5: Fix a required Input Inside a Hidden Tab Blocking Submit
  • SQL Server: Fix ROW_NUMBER Ties Reordering Between Identical Runs
  • C#: Fix an Enum HasFlag Returning True for the Zero Value
  • WordPress: Fix Featured Images Vanishing After a CDN Migration
  • Photoshop: Fix Content-Aware Fill Smearing a Repeating Pattern
  • Asp.Net Core: Fix Antiforgery Tokens Rejected Behind a Reverse Proxy

Most Viewed Posts

  • How to make theater mode the default for Youtube (1,055)
  • Get the User Name and Domain Name from an Email Address in SQL (981)
  • How to add default value for Entity Framework migrations for DateTime and Bool (977)
  • Get the First and Last Word from a String or Sentence in SQL (858)
  • How to select distinct rows in a datatable in C# (854)

Recent Posts

  • C#: Fix a ConditionalWeakTable Entry Vanishing Too Soon
  • Docker: Fix a Stale COPY Layer After Editing .dockerignore
  • Photoshop: Fix a Pattern Overlay Scaling Wrong on a High-DPI File
  • SQL Server: Fix a Computed Column Index Skipped by Implicit Cast
  • HTML5: Fix a required Input Inside a Hidden Tab Blocking Submit

Social

  • ErcanOPAK.com
  • GoodReads
  • LetterBoxD
  • Linkedin
  • The Blog
  • Twitter
© 2026 Bits of .NET | Built with Xblog Plus free WordPress theme by wpthemespace.com