Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

157
Views
Optional chaining doesn't work on Node 16.4

I have tried this syntax in VSCode and Coderpad (both use Node version 16.4).

let x = {}
x?.something.foo

As far as my understanding goes, this code shouldn't throw an error now, but return undefined. The feature optional chaining should be available in Node v14+ but for some reason it doesn't work in my VSCode and also in Coderpad.

Thought why?

about 4 years ago · Juan Pablo Isaza
1 answers
Answer question

0

x is an existing object for which you want to allow the something property to be undefined. Hence, the correct syntax should be x.something?.foo

The syntax x?.something.foo means: allow an object x to be undefined, but if it isn't, return the value of the property chain something.foo. Since in this case x is defined, but x.something isn't, you'll get an error (unless you use x?.something?.foo).

about 4 years ago · Juan Pablo Isaza Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!