[coc.nvim] Failed to load the ESLint library for the document test.js #11

kevindashgit · 2019-04-26T20:45:03Z

I'm just now getting more "serious" about using Coc in my development machine - and I'm trying to use this extension as a replacement for ALE by suggestion from this article but unfortunately I'm getting some pretty buggy behavior.

When I load a javascript file (any file) I see warnings that are legit warnings (like the neovim "sign" / gutter indicator is there) but I see the error in this issue summary at the bottom

However, if I play around enough (not sure what triggers it, but spamming $ and 0 in normal mode on a line where a sign exists eventually triggers the expected warning (and btw this one in particular I'd love to turn off but I realize its an existing annoyance for others):

I did try `:CocUpdateSync and got this output:

:!yarnpkg upgrade --latest --ignore-engines
[No write since last change]

yarn upgrade v1.13.0
warning package.json: No license field
warning No license field
warning No license field
warning No license field
[1/4] Resolving packages...
warning coc-prettier > prettier-eslint > eslint > file-entry-cache > flat-cache > circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
warning coc-prettier > prettier-stylelint > stylelint > autoprefixer > browserslist@2.11.3: Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.
[2/4] Fetching packages...
[3/4] Linking dependencies...
warning "coc-prettier > prettier-tslint@0.4.2" has unmet peer dependency "typescript@^2.5.3 || ^3.0.0".
warning "coc-prettier > prettier-tslint > tslint@5.16.0" has unmet peer dependency "typescript@>=2.1.0 || >=2.1.0-dev || >=2.2.0-dev || >=2.3.0-dev || >=2.4.0-dev || >=2.5.0-dev
|| >=2.6.0-dev || >=2.7.0-dev || >=2.8.0-dev || >=2.9.0-dev || >=3.0.0-dev || >= 3.1.0-dev || >= 3.2.0-dev".
warning "coc-prettier > prettier-tslint > tslint > tsutils@2.29.0" has unmet peer dependency "typescript@>=2.1.0 || >=2.1.0-dev || >=2.2.0-dev || >=2.3.0-dev || >=2.4.0-dev || >=
2.5.0-dev || >=2.6.0-dev || >=2.7.0-dev || >=2.8.0-dev || >=2.9.0-dev || >= 3.0.0-dev || >= 3.1.0-dev".
[4/4] Rebuilding all packages...
success Saved lockfile.
warning No license field
success Saved 365 new dependencies.

Is that warning anything special?

I'd greatly appreciate any help here :)

:CocInfo Output

## versions

vim version: NVIM v0.3.2-dev
node version: v10.15.3
coc.nvim version: 0.0.65-5effa64974
term: iTerm.app
platform: darwin

## Error messages

## Output channel: prettier


[Trace - 4/26/2019, 1:34:45 PM:] Formatted file: file:///Users/foobar/temp/test.js


[Trace - 4/26/2019, 1:34:45 PM:] Prettier format edits: [
  {
    "range": {
      "start": {
        "character": 0,
        "line": 0
      },
      "end": {
        "character": 0,
        "line": 16
      }
    },
    "newText": "var debug = require(\"debug\");\n\n// A comment\n\nfunction sayHi() {\n  console.log(\"hi\");\n}\n\naksayHi();\n\nasdfl;\nj: w;\n"
  }
]


## Output channel: tsserver

[Info  - 1:34:32 PM] Forking TSServer
PATH: /Users/foobar/.yarn/bin:/Users/foobar/.config/yarn/global/node_modules/.bin:/var/folders/nl/ry78xgy13djdd9ntz2vfkq240000gn/T/fnm-shell-299137/bin:/Users/foobar/.fnm:/opt/local/bin:/opt/local/sbin:/Users/foobar/.pyenv/plugins/pyenv-virtualenv/shims:/Users/foobar/.pyenv/shims:/Users/foobar/.pyenv/bin:/usr/local/sbin:/usr/local/bin:/Users/foobar/.cargo/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/VMware Fusion.app/Contents/Public:/usr/local/sbin:/usr/local/share/dotnet:~/.dotnet/tools:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Applications/Wireshark.app/Contents/MacOS:/Users/foobar/.yarn/bin:/Users/foobar/.config/yarn/global/node_modules/.bin:/var/folders/nl/ry78xgy13djdd9ntz2vfkq240000gn/T/fnm-shell-3942512/bin:/Users/foobar/.fnm:/opt/local/bin:/opt/local/sbin:/Users/foobar/.pyenv/plugins/pyenv-virtualenv/shims:/Users/foobar/.pyenv/shims:/Users/foobar/.pyenv/bin:/Users/foobar/.cargo/bin 
[Info  - 1:34:32 PM] Started TSServer
{
  "path": "/Users/foobar/.config/coc/extensions/node_modules/coc-tsserver/node_modules/typescript/lib",
  "_pathLabel": "",
  "_api": {
    "versionString": "3.3.4000",
    "version": "3.3.4000"
  }
}

## Output channel: eslint

[Info  - 1:34:32 PM] ESLint server running in node v10.15.3

:CocConfig

{
  "suggest.echodocSupport": true,
  "suggest.maxCompleteItemCount": 20,
  "coc.preferences.formatOnSaveFiletypes": ["javascript", "typescript", "typescriptreact", "json", "javascriptreact"],
  "eslint.filetypes": ["javascript", "typescript", "typescriptreact", "javascriptreact"],
  "eslint.options": {
    "configFile": "~/.eslintrc"
  },
  "diagnostic.errorSign": "•",
  "diagnostic.warningSign": "•",
  "diagnostic.infoSign": "•"
}

The text was updated successfully, but these errors were encountered:

chemzqm · 2019-04-27T00:11:47Z

Make sure eslint can be resolve from your workspaceFolder https://github.com/neoclide/coc.nvim/wiki/Using-workspaceFolders or global npm modules.

You can disable suggest actions from tsserver https://github.com/neoclide/coc-tsserver#configuration-options.

VVoruganti · 2019-05-10T19:34:04Z

I am having the same issue no matter where I open a script file.

Not sure how to see if eslint can resolve.

chemzqm · 2019-05-10T19:56:57Z

Checkout your npm global module folder by npm root -g and make sure your have eslint inside that folder.

kevindashgit · 2019-05-10T21:06:24Z

@chemzqm you've spotted a recurring issue with my regular workflow - which is that I regularly switch node versions via nvm and so some versions I've properly installed eslint while others not so much. 🎆 👍

Bonus Points: I'd still prefer not to have to move cursor over "underlined" section to see the warning as reflected by the vim "sign" (marker indicating an issue on this line. Is there a setting to reveal the issue just by moving cursor to the erroneous line?

chemzqm · 2019-05-11T05:45:05Z

@kevindashgit Then you need to specify eslint.nodePath

dzintars · 2020-02-15T13:49:23Z

Same issue when opening Yarn 2 Berry PnP project.

fannheyward · 2020-02-15T14:23:09Z

@dzintars When using coc-eslint with yarn2 project, follow this:

yarn add @yarnpkg/pnpify add to your project
yarn pnpify --sdk

Now coc-eslint will find eslint automatically.

dzintars · 2020-02-15T14:35:24Z

@fannheyward Tnx. I already did that, but no luck. Will update this issue when will get into something. BTW... which is recommended method today to install plugins? :CocInstall coc-eslint or Plug 'neoclide/coc-eslint', {'do': 'yarn install --frozen-lockfile'}?

fannheyward · 2020-02-15T14:45:58Z

:CocInstall coc-eslint, extensions installed with :CocInstall can do auto-updating.

stiofand · 2020-04-25T12:23:42Z

I have had the same issue with eslint without success, I am unable to get coc working with either eslint or prettier, sadly I have to revert to another method until there is a solution for this.

emmtte · 2020-05-11T21:49:13Z

Same issue for me with coc-prettier and coc-eslint
After manually install dependencies on dev folder work like as expected
npm install --save-dev eslint prettier eslint-config-prettier eslint-plugin-prettier
(Node.js 14)

lauri-codes · 2020-05-21T07:45:26Z

I'm also experiencing the same issue. After installing with :CocInstall coc-eslint, I have eslint installed under the path reported by npm root -g. I only got eslint working after installing it locally for the project as suggested by @emmtte using the command npm install --save-dev eslint. My setup is:

coc-eslint 1.2.7
coc.nvim version: 0.0.78-42353685a1
vim version: NVIM v0.4.3
node version: v12.16.3

arbitrary-dev · 2020-09-06T07:33:16Z

For me the problem was that I've installed eslint using Yarn, and so I have to set:

"eslint.nodePath": "/home/user/.config/yarn/global/node_modules"

ghost · 2020-10-03T10:40:17Z

@chemzqm

Can I skip the error?

If I have a random js file somewhere not in project, then this error always happens.

I think this is supposed to be, but I want to skip the error if there is no eslint configuration.

chemzqm · 2020-10-03T14:08:43Z

You can create .vim/coc-setings.json at any parent folder of your file.

ghost · 2020-10-03T14:20:09Z

Oh.... I see.
So I need to create config file everytime I open random js file.

Um well, it can't be helped.
thanks

chemzqm · 2020-10-03T14:52:41Z

Or you can create a global eslint config file.

ghost · 2020-10-03T15:15:21Z

@chemzqm
I tried that!
In that case even if I'm in some project, coc will look to global eslint.

prettierrc.js behavior is good.
https://prettier.io/docs/en/configuration.html

The configuration file will be resolved starting from the location of the file being formatted, and searching up the file tree until a config file is (or isn’t) found.

chemzqm · 2020-10-03T15:17:26Z

You can use "root": true to make eslint not look up.

ghost · 2020-10-03T15:28:59Z

@chemzqm
Ah, thank you for reply, but no, in that case if there's no config in that workspace it causes the error,,,,,

（It would be great if this error goes to CocInfoLog. Not error in status line. But as you stated there is an way to handle this, so it's not critical. This is still great plugin.）

Clev7 · 2020-10-29T16:30:49Z

Checkout your npm global module folder by npm root -g and make sure your have eslint inside that folder.

This worked wonders! cd into that folder and do sudo npm install -g eslint and eslint should be where it needs to be

lambdaFun94 · 2020-12-29T16:15:44Z

Checkout your npm global module folder by npm root -g and make sure your have eslint inside that folder.

This worked wonders! cd into that folder and do sudo npm install -g eslint and eslint should be where it needs to be

Super helpful!

chemzqm closed this as completed Apr 27, 2019

billyvg mentioned this issue Feb 24, 2021

Not working with yarn2 / berry (PnP)? #105

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[coc.nvim] Failed to load the ESLint library for the document test.js #11

[coc.nvim] Failed to load the ESLint library for the document test.js #11

kevindashgit commented Apr 26, 2019

chemzqm commented Apr 27, 2019 •

edited

Loading

VVoruganti commented May 10, 2019

chemzqm commented May 10, 2019

kevindashgit commented May 10, 2019

chemzqm commented May 11, 2019

dzintars commented Feb 15, 2020

fannheyward commented Feb 15, 2020

dzintars commented Feb 15, 2020

fannheyward commented Feb 15, 2020

stiofand commented Apr 25, 2020 •

edited

Loading

emmtte commented May 11, 2020 •

edited

Loading

lauri-codes commented May 21, 2020

arbitrary-dev commented Sep 6, 2020

ghost commented Oct 3, 2020

chemzqm commented Oct 3, 2020

ghost commented Oct 3, 2020

chemzqm commented Oct 3, 2020

ghost commented Oct 3, 2020

chemzqm commented Oct 3, 2020

ghost commented Oct 3, 2020 •

edited by ghost

Loading

Clev7 commented Oct 29, 2020

lambdaFun94 commented Dec 29, 2020

[coc.nvim] Failed to load the ESLint library for the document test.js #11

[coc.nvim] Failed to load the ESLint library for the document test.js #11

Comments

kevindashgit commented Apr 26, 2019

chemzqm commented Apr 27, 2019 • edited Loading

VVoruganti commented May 10, 2019

chemzqm commented May 10, 2019

kevindashgit commented May 10, 2019

chemzqm commented May 11, 2019

dzintars commented Feb 15, 2020

fannheyward commented Feb 15, 2020

dzintars commented Feb 15, 2020

fannheyward commented Feb 15, 2020

stiofand commented Apr 25, 2020 • edited Loading

emmtte commented May 11, 2020 • edited Loading

lauri-codes commented May 21, 2020

arbitrary-dev commented Sep 6, 2020

ghost commented Oct 3, 2020

chemzqm commented Oct 3, 2020

ghost commented Oct 3, 2020

chemzqm commented Oct 3, 2020

ghost commented Oct 3, 2020

chemzqm commented Oct 3, 2020

ghost commented Oct 3, 2020 • edited by ghost Loading

Clev7 commented Oct 29, 2020

lambdaFun94 commented Dec 29, 2020

chemzqm commented Apr 27, 2019 •

edited

Loading

stiofand commented Apr 25, 2020 •

edited

Loading

emmtte commented May 11, 2020 •

edited

Loading

ghost commented Oct 3, 2020 •

edited by ghost

Loading