Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Parsing error: Cannot read property ecmaFeatures of undefined when eslint also installed
See original GitHub issueWhen eslint and xo are both installed, the run fails with: Parsing error: Cannot read property ecmaFeatures of undefined
https://travis-ci.org/graingert/eslint-ecma-featured-of-undefined/jobs/401852495 https://github.com/graingert/eslint-ecma-featured-of-undefined/commit/a6d1d12b8d3f0ab437f9c1d086825370fb860e03
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Line 0: Parsing error: Cannot read property 'map' of undefined
This error occurs because react-scripts has a direct dependency on the 2.xx range of @typescript-eslint/parser and ...
Read more >parsing error: cannot read properties of undefined ... - You.com
I'm trying to use the eslint command on my angular project in the terminal to check a typescript component for errors. I'm getting...
Read more >eslint/eslint - Gitter
This error "Cannot read property 'Scope' of undefined" triggers only on *.jsx files and always points to their very first line, but since...
Read more >Migrating to v6.0.0 - ESLint - Pluggable JavaScript Linter
Plugin authors may need to update installation instructions ... sourceType: "module" parser option is set while ecmaVersion is set to 5 or left...
Read more >Local Install of ESLint Breaks In-Editor Linting
However, if I install ESLint locally as a npm package, ... are now no linter errors present but there is a linter warning...
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 Free
Top 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
Hi @pvdlg , I just ran into this issue too when trying to upgrade eslint to 5.2.0. Upgrading XO to latest version 0.21.1 didn’t help, but manually installing eslint-plugin-node ^7.0 solved the issue:
npm install --save-dev --save-exact eslint-plugin-node@7.0.1FWIW, the problem also disappears after upgrading eslint-plugin-node from ^6.0.0 to ^7.0.0 for xo. I haven’t tested it extensively though, and it’s a major version bump.