A baseline needed to be updated after the merge from master. I'll merge this after CI finishes running.

Hi, I am able to compile successfully but at runtime, I receive a Promise.any is undefined error. I am using typescript 3.9.5 in my project. This is my tsconfig:

{
  "compilerOptions": {
    "target": "ES6",
    "module": "commonjs",
    "strict": true,
    "esModuleInterop": true,
    "outDir": "dist",
    "lib": [
      "dom",
      "esnext",
      "esnext.promise"
    ],
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "forceConsistentCasingInFileNames": true,
    "inlineSourceMap": true,
  }
}

Any feedback would be much appreciated.

Hi, I am able to compile successfully but at runtime, I receive a Promise.any is undefined error. I am using typescript 3.9.5 in my project. This is my tsconfig:

{
  "compilerOptions": {
    "target": "ES6",
    "module": "commonjs",
    "strict": true,
    "esModuleInterop": true,
    "outDir": "dist",
    "lib": [
      "dom",
      "esnext",
      "esnext.promise"
    ],
    "noUnusedLocals": true,
    "noUnusedParameters": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true,
    "forceConsistentCasingInFileNames": true,
    "inlineSourceMap": true,
  }
}

Any feedback would be much appreciated.

same with me. typescript 3.9.7

@mt-yannick @alongite what VM are you using? I looked at https://caniuse.com/#search=Promise.any and it's only on recent versions of Chrome and Firefox as far as I can tell. It's not in Node 14 yet.

@sandersn Oh! Thank you for clarifying!! So if I understand correctly, this PR implements the types for Promise.any, and specifying "esnext.promise" in compilerOptions.libs will make the compiler aware that Promise.any exists, but we are still responsible for assuring that an implementation exists!

@mt-yannick yes, that's exactly right. Stuff in "esnext" is going to be very new, so you may need to provide your own polyfill.