resolvePaths option works differently with import compared to require

[jordanbtucker]

When using the resolvePaths setting to set the paths where eslint should look when resolving module specifiers, import statements resolve as expected, but require statements don't.

See my minimal reproducible example.

The way eslint-plugin-n handles import statements is that it pretends that the source module is in each of the directories specified by resolvePaths, however it does not do this for require statements.

---

Note that the paths property of the options parameter of resolve.sync should work like the paths property of the options parameter of require.resolve, but it doesn't.

[scagood]

#139 has just been merged which may help with this as both import and require use the same code 😀