Better errors when using properties/methods from newer versions of ECMAScript

[DanielRosenwasser]

This is kind of the progression of #25309, and this issue's fix should be inspired by #27034.

---

Lots of users seem to be confused by misconfiguration when using popular new methods added to built-in types. A recent example is #40319.

The idea here come up with a static list of methods added to

• Array
• String
• RegExp
• ObjectConstructor
• Promise
• Map
• Set
• Iterator
• AsyncIterator

in newer versions of ECMAScript. These can be found in src/lib.

When a user tries to access a property on any of these types, and that type appears in the list, we can provide a suggestion to set their lib or target (which we've done in other error messages). For example:

Property '{0}' does not exist on type '{1}'. Do you need to change your target library? Try changing the `lib` compiler option to '{2}' or later.

[sarathps93]

Is it ok if I take this up as my first issue? @DanielRosenwasser

[Vboivin]

Hey @sarathps93, are you still working on this? If not, I'll try this issue

[sandersn]

As a first step, it would help to have a list of methods with their respective versions added to this bug, if anybody is looking for an easy way to help with no overhead.

[Vboivin]

@sandersn Great idea. I am actually working on it since @sarathps93 did not respond.
Here is the mapping I have done by taking a quick look at the declaration files:

es2016

• Array.includes()

es2017

• String.padStart()
• String.padEnd()
• Object.values()
• Object.entries()
• Object.getOwnPropertyDescriptors()
• Intl
• TypedArrays
• SharedMemory

es2018

• Promise.finally()
• RegExp
• Intl2018
• AsyncGenerator
• AsyncIterable

es2019

• Array.flat()
• Array.flatMap()
• Object.fromEntries()
• String.trimStart()
• String.trimEnd()
• String trimLeft()
• String.trimRight()
• Symbol.description

es2020

• BigInt
• Intl2020
• Promise.allSettled()
• String.matchAll()
• RegExp.matchAll()

[Vboivin]

@DanielRosenwasser @RyanCavanaugh @sandersn I attempted a solution for this problem, it might not be the best, waiting for feedback!

[DanielRosenwasser]

Thank you @Vboivin!