Object access reports error after upgrading to TypeScript 5.5

🔎 Search Terms

"noUncheckedIndexedAccess", "Object is possibly 'undefined'."

🕗 Version & Regression Information

• This changed between versions 5.4.5 and 5.5.3

⏯ Playground Link

https://www.typescriptlang.org/play/?noUncheckedIndexedAccess=true&ts=5.5.3#code/DYUwLgBAzmBOBc04EsB2BzCAfCBXVAJiAGZogEDcAUMsRABQCyAhmABYB0szhA9gLb0AlBAA8EAAwcAjCIDeVCElgQAvBABEzDVQC+VKgGNeqGBGaHDiORADaqZvxCIYsNOgC6iVLn4AjEBVdNQg5XWpaBlcIAEJ1H2BgeUVzS1tXDwgAfiz1CWolC0N0uA8AajLqfSA

💻 Code

// @strict: true
let str: string | undefined;
if (Math.random() < 0.1) {
  str = "a"
}

const acc: { [name: string]: number } = {};
if (str != null) {
  acc[str] ??= 0;
  acc[str]++; // In TS 5.5: Object is possibly 'undefined'. (2532)
}

🙁 Actual behavior

In TS 5.5.x, with noUncheckedIndexedAccess enabled, acc[str]++; reports an error "Object is possibly 'undefined'. (2532)".

🙂 Expected behavior

In TS 5.4.x and before, no errors were reported.

Additional information about the issue

I admittedly didn't do a very deep dive on the root cause here, but wanted to file an issue because intuitively it felt unexpected when upgrading to TS 5.5 that the above code now fails type-checking. Apologies if I missed an existing issue for this or something in the release notes!

Inizia dal repro collegato di TypeScript Playground e confronta le relative diagnostiche con 5.4.5 e 5.5.3, concentrandoti su noUncheckedIndexedAccess, nullish assignment e indexed access. Traccia il comportamento del checker responsabile della regressione e aggiungi un test di regressione; il lavoro è completato quando l'esempio non segnala più la diagnostica errata, mentre i controlli di sicurezza pertinenti rimangono intatti.