Index signatures in type definitions: now we have `noUncheckedIndexedAccess`, include or omit `undefined`?

lib Update Request

Before we had noUncheckedIndexedAccess, it was common practice to add undefined to an index signature as a workaround. For example:

• https://github.com/microsoft/TypeScript/issues/13792 in which the index signature inside DOMStringMap (lib.dom.d.ts) was modified to include undefined.
• https://github.com/DefinitelyTyped/DefinitelyTyped/pull/43931 in which all index signatures in @types/node were modified to include undefined (e.g. ProcessEnv and ParsedUrlQuery).

However, it seems this workaround wasn't extended to all index signatures, e.g.
RegExpMatchArray['groups'] in lib.es2018.regexp.d.ts and PropertyDescriptorMap in lib.es5.d.ts.

Now we have noUncheckedIndexedAccess I would like to ask what the best way forward is regarding these workarounds? For people who enable noUncheckedIndexedAccess, these workarounds are redundant. For people who don't enable noUncheckedIndexedAccess, these workarounds are still necessary—but potentially not always desirable since it forces a higher level of strictness.

It seems inconsistent that some index signatures use this workaround and others do not, so I think we should decide either to use this workaround in all index signatures or remove it from all index signatures and suggest people use noUncheckedIndexedAccess.

Including undefined creates a few problems, for example:

declare const v: DOMStringMap;

Object.values(v).map((value) => {
    // Expected: string;
    // Actual: string | undefined; ❌
    value;
});

for (const value of Object.values(v)) {
    // Expected: string;
    // Actual: string | undefined; ❌
    value;
}

const test: DOMStringMap = {
    // This should error
    foo: undefined
}

If the TypeScript team can decide the best way forward then this will also provide some guidance to the community—for example we're trying to decide what the best option is for @types/node: https://github.com/DefinitelyTyped/DefinitelyTyped/pull/51177.

Commencez par comparer les signatures d’index dans lib.es2018.regexp.d.ts, lib.es5.d.ts et lib.dom.d.ts, puis examinez les exemples de l’issue concernant noUncheckedIndexedAccess. L’issue ne précise pas quelle politique adopter ; il faudrait donc que l’équipe prenne une décision avant de mettre à jour les définitions concernées et de vérifier son impact sur le comportement cité.