"Resolve error: unable to load resolver "node""

Question

I have spent the day wrestling with standardJS and package.json in a project.

Just when I thought I had fixed some no-def issues when upgrading to standard 11, I now face multiple:

error  Resolve error: unable to load resolver "node"  import/no-duplicates

So going to back to basics, do I really need "eslint" installed for standardJS to work? The project does seem to require "babel-eslint" for some arrow functions to work .

Is there anything else I can do to try resolve these CI errors ?

Maybe it's a Travis issue, or a npm i and meteor npm i issue.

Answer 1

I had to explicitly installeslint-import-resolver-node . There was a recent update to the eslint-plugin-import that did not correctly link eslint-import-resolver-node . The following command will install the missing package and get things working:

npm install -D eslint-import-resolver-node

Answer 2

For some reason, npm 6 install was messing around with meteor npm 's in-built version at 4. The CI fix was to override the default Travis install phase .

Nonetheless I am still wondering if I need eslint dependency in my project.