eslint-plugin-import: eslint-module-utils 2.5.1 broken

Hey, when using eslint-module-utils 2.5.1, my eslint stops being able to resolve most imports. I receive lots of errors of this type:

1:1   error    Resolve error: unable to load resolver "node"    import/namespace

Pinning it at 2.5.0 makes all the errors go away. I won’t ass lots of logs here as I assume it’s something obvious. If it turns out to be more complicated, let me know and I’ll give a full description of my setup. This was tested both with eslint 5.16.0 and 6.8.0.

About this issue

Original URL
State: closed
Created 4 years ago
Comments: 21 (9 by maintainers)

Commits related to this issue

make dependency on eslint-import-resolver-node explicit https://github.com/benmosher/eslint-plugin-import/issues/1604 — committed to tobiipro/eslint-config-firecloud by andreineculau 4 years ago
make dependency on eslint-import-resolver-node explicit https://github.com/benmosher/eslint-plugin-import/issues/1604 — committed to tobiipro/eslint-config-firecloud by andreineculau 4 years ago
utils: Makes the loader resolution more tolerant Fixes #1604. Fixes #1603. — committed to arcanis/eslint-plugin-import by arcanis 4 years ago
utils: [Fix] Makes the loader resolution more tolerant Fixes #1604. Fixes #1603. — committed to arcanis/eslint-plugin-import by arcanis 4 years ago

Most upvoted comments

I can confirm that v2.5.2 fixes it for me! I was able to remove the explicit dependency on eslint-module-utils. Thank you for the wonderfully quick turnaround, @ljharb!

I’m sorry that I wasn’t able to get you a repro repo. I’m glad you were able to find a solution despite that.

jasonaowen on Jan 13, 2020

By the way, thank you @ljharb for maintaining this tool and responding on the weekend! And @johanneswilm, thank you for opening this issue - it helped me figure things out more quickly.

jasonaowen on Jan 11, 2020

Yes, thanks for all your work @ljharb

johanneswilm on Jan 12, 2020

I tried again. I removed the pinning of eslint-module-utils and instead pinned eslint-import-resolver-node to 0.3.3. It did not work.

Then I pinned eslint-import-resolver-node to 0.3.3 and eslint-module-utils to 2.5.1. Also this did not work.

The only thing that has worked so far is to pin eslint-module-utils to 2.5.0. Whether or not I mention either 0.3.2 or 0.3.3 of eslint-import-resolver-node in package.json seems to make no difference at all.

johanneswilm on Jan 11, 2020