Promise.all weirdness in nightlies

[DanielRosenwasser]

The playground seems to have a lot of weirdness [...] with Promise.all. Things like signature help don't even seem to work correctly. I'm not sure exactly what the problem is, but if you do try that code out locally with a nightly version of TypeScript, it should all work fine.

Originally posted by @DanielRosenwasser in microsoft/TypeScript#33752 (comment)

[DanielRosenwasser]

The code that we were trying out had some issues:

(async () => {
    const [num1, num2] = await Promise.all([Promise.resolve(1), Promise.resolve(null)]);
    num1.toString();
})

it had different error messages than locally, and it had problems with triggering signature help. Very strange.

[DanielRosenwasser]

(maybe because of lib.d.ts ordering? but that doesn't explain the signature help stuff)

[orta]

I think all the filenames for the lib.d.ts are hardcoded, is there a chance that 3.9 adds a new file?

[DanielRosenwasser]

I don't think so, but @rbuckton would have more context here.

[DanielRosenwasser]

I think that microsoft/TypeScript#37510 fixes this.

[DanielRosenwasser]

Verified that it does! The problem is that TypeScript internally has a list for ordering the .d.ts files, but it differs from the /// <reference lib="..." /> directives which I believe the playground crawls to concatenate/build.

Sorry for the confusion on this end.

[orta]

👍 thanks!