Closed parker789 closed 4 years ago
What is "coc-eslint"?
https://github.com/neoclide/coc-eslint - it's a an eslint plugin for vim
And what working directory is it using to invoke eslint? All commands should always be invoked from a project’s root.
Hmm, this I'm not 100% sure on.
Ive run eslint.trace.verbose to check the language server logs.. and there are some line items within there which make me think it's invoking eslint correctly.. I think this log may be outside the scope of this question, but if not here you go.. my projects root is Dev/web
What versions of all eslint stuff are you using?
"eslint": "^5.16.0",
"eslint-config-airbnb": "^17.1.0",
"eslint-config-prettier": "^4.1.0",
"eslint-config-react-app": "^3.0.8",
"eslint-loader": "^2.1.2",
"eslint-plugin-flowtype": "2.39.1",
"eslint-plugin-import": "^2.16.0",
"eslint-plugin-jsx-a11y": "^6.2.1",
"eslint-plugin-prettier": "^3.0.1",
"eslint-plugin-react": "^7.12.4",
Do you get the same warning on the command line?
The entire flow of prettier -> eslint while using prettier-eslint
confuses me.. but I tried running npx eslint --fix <file>
from command line on the file I'm seeing that error while in vim, but I don't see anything in the command line output.
Something to mention might be this warning is only occurring 1 time. After I run the first lint job everything works fine without warnings
Maybe the issue is that you’re invoking prettier directly? prettier works best imo when it’s only ever invoked by eslint, using eslint-plugin-prettier.
I feel like I read something where eslint-plugin-prettier was outdated and prettier-eslint was the new way to run the combo. not sure tho.. :( ill look into it more and see if i can figure things out! thanks for the help
it's not; afaik prettier-eslint isn't even updated anymore.
I'll close this for now, but happy to keep discussing, and happy to reopen it if it turns out there's something this plugin needs to fix!
I know there are plenty of issues already in the works with this exact same warning message.. but I believe my use case is slightly different.
I'm using
coc-eslint
andcoc-prettier
with the"prettier.eslintIntegration": true
option. With this option set tofalse
I don't see this warning, but then obviously some formatting is not caught and auto formatted based on eslint rules. I don't know if this is an issue with coc or any of the extensions I'm using along with it, but I figured I'd ask here, because there were dead ends when asking directly within those libraries support pages.I've run
npx eslint --print-config .eslintrc
with the following output. im at a loss..