Linting not running on jsx files
See original GitHub issueIt may be something in my setup, but AFAIK nothing has changed. Linting has stopped running on JSX files, where I am pretty sure it did in the recent past (I got a VSCode update recently)
When I run ./node_modules/.bin/eslint --ext .js,.jsx src test
locally it finds issues in .jsx files, however not within the VSCode “Problems” tab
I went into my VSCode settings and have added "eslint.options": { "extensions": [".jsx", ".js"] }
and that isn’t helping either.
Am I doing it wrong?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
ESLint configuration for JSX - reactjs - Stack Overflow
In order to lint JSX files configuration alone is not enough. Your configuration looks fine (although you probably don't need babel-eslint ...
Read more >Linting React JSX with ESLint (in ES6) | egghead.io
We walk through setting up ESLint in a project, using the eslint --init CLI tool with the JSX and ES6 options, writing a...
Read more >Set up ESLint and lint-staged for JS/JSX/React project - Medium
A linter or lint refers to tools that analyze source code to flag programming errors, bugs, stylistic errors, and suspicious constructs.
Read more >React Native development tools - Part 1: Linting tools - Pusher
If your text editor shows something similar to the one above, then the linter is working. If not, then it's either you haven't...
Read more >React JavaScript Tutorial in Visual Studio Code
Linting. Linters analyze your source code and can warn you about potential problems before you run your application. The JavaScript language services included ......
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
FWIW, I found out the issue…my
*.jsx
files were being classified asJSX
instead ofJavascript React
, I believe due to another extension I had added. I removed the extension (but was also fixed by just adding ‘jsx’ to theeslint.validate
settings as you had suggested @dbaeumer - thanks!Had a fun time learning how to run an extension in the Extension Development Host and debug it along the way, which was fun 😃
@touzoku See my comments in https://github.com/Microsoft/vscode-eslint/issues/271