TS2339: Property 'bar' does not exist on type 'never' (strictNullChecks)

[maksimr]

Example code:

index.js

const [foo] = [null];
console.log(foo?.bar);

tsconfig.json

{
  "compilerOptions": {
    "target": "es6",
    "allowJs": true,
    "checkJs": true,
    "noEmit": true,
    "strictNullChecks": true,
    "moduleResolution": "node",
    "resolveJsonModule": true
  }
}

Command:

tsc

AR:

error TS2339: Property 'bar' does not exist on type 'never'.

2 console.log(foo?.bar);
                   ~~~
Found 1 error.

ER: No error

---

Typescript version 4.1.2

If change the code on:

const bar = [null];
const foo = bar[0];
console.log(foo?.bar);

All works fine

[RyanCavanaugh]

By what justification should this not be an error? This code doesn't make any sense.

[maksimr]

@RyanCavanaugh this is just a minimal reproducible example without any attached business logic to the code. The issue that typescript throws error when we handle null value.
Code like this

const bar = [null];
const foo = bar[0];

does not throw error.

In real world use case we use useState with initial value null and after that we set an object. We do the same null check but typescript throw error and this happens only when destruction is used

P.S.
Example of code similar to setState even with explicit type definition and without destruction

/**
 * @type {{bar:string}|null}
 */
let foo = null;
setState();
console.log(foo?.bar);

function setState() {
  foo = {bar: 'zoo'};
}

This code still throw

Property 'bar' does not exist on type 'never'.

6 console.log(foo?.bar);

[typescript-bot]

This issue has been marked 'Working as Intended' and has seen no recent activity. It has been automatically closed for house-keeping purposes.

[RyanCavanaugh]

Seems like you're talking about #9998 then

[maksimr]

@RyanCavanaugh kind of... mostly about optional chaining foo?.bar and strict null check. What I want is eliminate Property '<name>' does not exist on type 'never'. error without disabling strict null check. For me in the code above chaining operator should be enough to say typescript analyzer that I know about possible null value and cover it by optional chaining operator ? so all null safe :)
Thanks