Post

Convince me I am wrong: This should not be a type error, right? - I asserted it’s an object - I am using `?.` for property access www.typescriptlang.org/play/#code/G...

Jack Franklin

@jackf.io

10 July 2025

`typeof null === 'object'` so I think you might need to check for null. And then I tend to find 'a' in x more reliable in TS

Surma

@surma.dev

Right, I know how to work around it. But I am asking: Shouldn’t this be accepted by the type checker (because `null?.a` is perfectly valid)

10/7/25, 4:07 pm0 reposts1 like

Tim Fish

@timfish.dev

10 July 2025

The issue isn't the null. `object?.a` is not valid!

Why not?

That's just how the object type works in typescript. You're asserting it's an object and then trying to use it like `any` but it's not equivalent.

Surma

@surma.dev

10 July 2025

Yes. I know how typescript currently works. I'm claiming that TS should change it's behavior here (hence why I said "this should not be a type error, right?"). I thought you were saying that what I was doing here is wrong at the type theory level, which I don't think is the case.

Jack Franklin

@jackf.io

11 July 2025

Ah, misunderstood you!