Repository: TypeScript
Issue: capitalization of es2017 in error message does not match capitalization of ES2017 autocomplete suggestion
Labels: Suggestion,Experience Enhancement

## If the maintainers of this repository think this issue is worth considering, I would like to contribute the fix for it.

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

<!--
  What search terms did you use when trying to find an existing bug report?
  List them here so people in the future can find this one more easily.
-->
"capital ES" "capitalization ES"
### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about capitalization.

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?target=1&ts=4.3.0-dev.20210227#code/PTAEHUFMBsGMHsC2lQBd5oBYoCoE8AHSAZVgCcBLA1UABWgEM8BzM+AVwDsATAGiwoBnUENANQAd0gAjQRVSQAUCEmYKsTKGYUAbpGF4OY0BoadYKdJMoL+gzAzIoz3UNEiPOofEVKVqAHSKCJyCNIh4APLSAFagALygAN4AvgDcitExkLCoAToM0Oz6ABQRWQCUGSoAmkYI7NCuqGqcANag8ABmIjQUXi1OKBJMggBcysCToKAAtKAAgqAEjBZoGO6e3oQk5FR9XuIrDGsS2E6gnPAt-cwmZqDSTgxt03OLy6uWGJAAHkSUZCcGgSeSaHy7fw0QR4YEMX78FygeyOSzYUAAVQASgAZYSglqdFqQMiCN7zJaCFzSeC-dagP4AihAkFg0DcChdLokyDAkxIAgUdxkUDchiodhOYTdba+PbURTBeChGhmACivwYiBWkAAao4KAxpO4EqAAEQACRg0Aw4HgZCaZqVoXg7gCNuYJXVmu17n1lCN7gqipUOA2HjIXkQ9ucNPYNGJbjMzHYDGYkH4sGg6g6RvgehEXjNGq1OsEZs6IrN4AcqAA5MIAHKQCRmoIqSLEsigwQZrSQaGoRwKVzSPCgJzRnS3LD6FAIRAs4RIxMSe1NEQGDgi44sNhcbhBGZAA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
const myObj = {};
Object.values(myObj);
```
with "Target:" set to a pre-ES2017 example, like ES5.
### 🙁 Actual behavior

<!-- What happened, and why it was wrong -->
On hover, the error message says, "Property 'values' does not exist on type 'ObjectConstructor'. Do you need to change your target library? Try changing the `lib` compiler option to 'es2017' or later.(2550)"

The capitalization in this error message does not match the auto-generated capital "ES2017" suggestion in VSCode when filling out the `lib` compiler option.
### 🙂 Expected behavior

<!-- What you expected to happen instead, and why -->
For consistency, I think the error message should say, "Property 'values' does not exist on type 'ObjectConstructor'. Do you need to change your target library? Try changing the `lib` compiler option to 'ES2017' or later.(2550)", instead.

Here, the capital "ES2017" matches the suggested "ES2017" that appears when typing in a `tsconfig.json` file in VSCode.