-
-
Notifications
You must be signed in to change notification settings - Fork 26.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
visual studio code eslint support #1955
Comments
Can we trace this down to any specific VSCode version when this stopped working (I haven't tested this myself)? It may be a regression on their end. Otherwise, we may need to update the documentation to reflect this change. |
@tzapu I have observed similar behavior in |
@Timer @anilreddykatta i noticed this on Version 1.11.1 (1.11.1) so so far, 1.11.1 & 1.11.2 seem not to be working cheers |
Not working here neither, I'm on version 1.11.2. |
Hi, I maintain the ESLint extension for VS Code and got here due to microsoft/vscode-eslint#230. I created a react app using
things started to work for me. Is there something I am missing ? |
i think the confusing bit is that the docs are saying that it just works, you don't need to add anything, as the eslint extension in vscode auto detects create react app's eslint rules hope this helps |
To make setup for users easier could the |
I don’t think we’ll be creating |
@gaearon |
Yes. In the browser/cli, we hardcode ESLint to use the I think it’s fine if we encourage people to create |
Does this solve the issue? |
this seems like satisfactory solution, it's clear enough, it works, all is good in the world again. thank you very much |
Sounds great. Sorry for the trouble. 😛 |
I've tried both things ( |
adding eslintConfig to package.json works for me |
Add eslint config line facebook/create-react-app#1955 Add .env file To allow using absolute path for imports https://medium.com/@ktruong008/absolute-imports-with-create-react-app-4338fbca7e3d
Description
The docs here https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md mention that vs code should support the eslint config without doing anything extra
in practice, with latest versions of everything, i still had to add .eslintrc containing
{ "extends": "react-app" }
in order for the editor to load a configExpected behavior
VS Code ESLint plugin automatically detects Create React App's configuration file
Actual behavior
VS Code ESLint plugin needs and .eslintrc file to detect any config
Environment
Run these commands in the project folder and fill in their results:
npm ls react-scripts
└── react-scripts@0.9.5
node -v
v7.8.0
npm -v
4.2.0
macOS
I am not sure if this is a bug or a lack in documentation or I m just doing something wrong.
If it's the docs i can make a pull request I guess
Cheers
The text was updated successfully, but these errors were encountered: