ES3 reserved words
See original GitHub issueThe issue: https://github.com/zloirock/core-js/issues/980
In the code used char
as a variable name. The ESLint config contains ecmaVersion: 3
, till this week here was used the default ESLint parser. char
is a ES3 reserved word:
ESLint parsed it without any errors or warnings. However, this code might not work in some ES3 engines.
Issue Analytics
- State:
- Created 2 years ago
- Comments:22 (18 by maintainers)
Top Results From Across the Web
Keywords and reserved words in JavaScript
The filters below show which are keywords, and which are reserved words in different versions of ECMA ... The reserved words in ES2...
Read more >babel/plugin-transform-reserved-words
This plugin, to be used when targeting ES3 environments, renames variables from that set of words.
Read more >9. Reserved Words | Javascript: Object Oriented Programming
Chapter 9. Reserved Words. This appendix provides two lists of reserved keywords as defined in ECMAScript 5 (ES5). The first one is the...
Read more >[MS-ES3]: [ECMA-262-1999] Section 7.5.3, Future Reserved Words ...
JScript 5.x only considers the following to be FutureReservedWords: class, const, debugger, enum, export, extends, import, super.
Read more >reserved-keywords - npm
Tiny package for detecting reserved words. Reserved Word is either a Keyword , or a Future Reserved Word , or a Null Literal...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Opened a PR: https://github.com/eslint/espree/pull/513
That’s what I was thinking, too.
Yes. Reserved words were completely illegal in ES3.