Incorrect ecmaVersion suggests only the old-style ES versions
See original GitHub issueTell us about your environment
- ESLint Version: 3.8.1
- Node Version: 3.9.0
- npm Version: 3.10.8
What parser (default, Babel-ESLint, etc.) are you using? default
Please show your full configuration:
'use strict';
module.exports = {
parserOptions: {
ecmaVersion: 2018,
},
};
What did you do? Please include the actual source code causing the issue.
eslint .
What did you expect to happen? An error message that would mention the 2015, 2016 & 2017 options.
What actually happened? Please include the actual, raw output from ESLint. It prints:
Parsing error: ecmaVersion must be 3, 5, 6, 7, or 8
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:8 (8 by maintainers)
Top Results From Across the Web
eslint Parsing error: ecmaVersion must be 3, 5, 6, or 7
ESLint currently supports versions 3, 5, 6 (es2015), 7(es2016) and 8(es2017). If you are having trouble enabling es2017, verify that your ...
Read more >eslint | Yarn - Package Manager
ESLint is a tool for identifying and reporting on patterns found in ECMAScript/JavaScript code. In many ways, it is similar to JSLint and...
Read more >demo-outil-edition - node_modules - eslint - CHANGELOG.md
39dfe08 Update: false positives in function-call-argument-newline (fixes ... 9b86167 Docs: Add new ES environments to Configuring ESLint ...
Read more >Language Options - ESLint - Pluggable JavaScript Linter
A pluggable and configurable linter tool for identifying and reporting on patterns in JavaScript. Maintain your code quality with ease.
Read more >Viewing online file analysis results for 'EmuTarkov-Server.exe'
Indicators. Not all malicious and suspicious indicators are displayed. Get your own cloud service or the full version to view all details.
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
I actually don’t think we should be outputting the possible version numbers at all. It should be fine to just say “Invalid ecmaVersion”, otherwise we’ll be stuck updating that message every year.
And if this is coming from Espree, then it would have to be changed there, not here.
@nzakas thanks!
Should have a PR open for this late today PST and will ref this issue when I do.