[Linter] Error running ESLint Error: require(...).getLocationFromRangeIndex is not a function(…)

[nwaywood]

ESLint is failing to run for me with eslint-plugin-prettier rules activated (i.e. with "rules": { "prettier/prettier": "error" } set).

This is the stacktrace from atom:

As it says in the stacktrace, the error comes from this file on line 30 where it calls require('eslint/lib/ast-utils').getLocationFromRangeIndex(...).

Upon inspection of eslint/lib/ast-utils I see that the function no longer exists. The function was removed in this commit.

[not-an-aardvark]

Does this still occur with eslint-plugin-prettier@2.0.1?

[nwaywood]

Yes. Here are the devDeps from my package.json

[nwaywood]

Not sure if this is important/relevant but this error only happens when the file does not conform to the prettier format. If a file is already formatted by prettier than the linter doesn't log this error

[not-an-aardvark]

Hmm, that's odd. You're right that the function from eslint/lib/ast-utils no longer exists, but the ternary expression here is intended to check for the existence of sourceCode.getLocFromIndex, which was added in the same commit that the other function was removed.

What version of eslint do you currently have installed? (Your package.json just shows ^3.14.1, but I'm wondering if there's a particular eslint version where this breaks. It seems to work fine for me with the latest version of eslint.)

[nwaywood]

Yes the version of eslint I am using is ^3.14.1, I just updated eslint to the latest (^3.18.0) and I get the same error. Would you like me to test a different version?

Edit: After restarting atom it works on version ^3.18.0! Thanks for your time, feel free to close issue :)

[not-an-aardvark]

From your stack trace screenshot, I see that you're using eslint from atom. Have you tried restarting atom? I wonder if it's caching the version of eslint somehow.

(Apart from that, I'm not sure what the problem would be given that it seems to be working on master and for other people.)

[nwaywood]

Sorry I made an edit to my previous comment, you most not have noticed it. After a restart of atom it is working now with version ^3.18.0 of eslint. I'll close this since its only an issue with an old version of eslint

[not-an-aardvark]

Great, glad to hear it's working now.