Hello, I am not sure if this is the right place for this but we got the below issue with version 4.7.0-dev.20220320 (this is automatically selected by VSCode) like the below image. We did some testing and noticed that this issue does not show up for version below 4.7.0, in our case 4.6.2 and 4.1.5 work fine. If this is not the right place for this, please let me know. Thanks

Context:

• We provide type safe fetch (its type is quite nested) which allows us to safely type the response based on the url of the request we are trying to make for a good dev experience
• We are getting the below error when we use our fetch in a Promise.all. My assumption is that Promise.all
  is trying to infer the type from our fetch type which is quite nested and caused this error on 4.7.0-dev.20220320

const [responseOne, responseTwo] = await Promise.all([ // it complains about the below error here
    fetch("https://something/v1", { req, timeout: 5000 }),
    fetch(
      "https://something/v2",
      { req, timeout: 5000 }
    )
  ])

@vietanhtran16 yes, the issue is not for bug report, please file a new issue. :)

@vietanhtran16 yes, the issue is not for bug report, please file a new issue. :)

Cool I will file a new one

@typescript-bot create release-4.7

Heya @DanielRosenwasser, I've started to create the release-4.7 branch for you. Here's the link to my best guess at the log.

Looks like it's probably failing because of the Node ESM stuff which we were hoping to unflag for the beta at the least. There's also some basic bug fixes I'd like us to pull in before beta, so maybe we'll go out on April 6th instead.

@typescript-bot create release-4.7

Heya @DanielRosenwasser, I've started to create the release-4.7 branch for you. Here's the link to my best guess at the log.