babel-eslint necessary when not using babel
See original GitHub issueI’m using the latest NodeJS without Babel and the latest eslint, but when I remove the parser
option from my eslintrc
, which is set to babel-eslint
and which I started using earlier when I was using babel, I get many parsing errors in my eslint output. Shouldn’t babel-eslint only be necessary when there’s no use of babel? At what point will eslint be able to handle official ES2017/8 code and I won’t need babel-eslint?
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (9 by maintainers)
Top Results From Across the Web
The State of babel-eslint
While Babel enables the use of experimental syntax, ESLint core only supports syntax once it reaches Stage 4 and is finalized in the...
Read more >babel/babel-eslint: A wrapper for Babel's parser used ... - GitHub
As of the v11.x.x release, babel-eslint now requires Babel as a peer dependency and expects a valid Babel configuration file to exist. This...
Read more >@babel/eslint-parser - npm
@babel/eslint-parser is a parser that allows ESLint to run on source code that is transformed by Babel. Note: You only need to use...
Read more >Updating babel-eslint to @babel/eslint-parser for React apps
As of the v11.x.x release, babel-eslint now requires Babel as a peer dependency and expects a valid Babel configuration file to exist. This ......
Read more >babel-eslint | Yarn - Package Manager
You only need to use babel-eslint if you are using types (Flow) or experimental features not supported in ESLint itself yet. Otherwise try...
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
Closing because this is working as intended.
Indeed, the default ecmaVersion shouldn’t be set to the latest, it should be set to the safest thing - which is ES5.