import/no-unresolved raises false positives in many projects

I think import/no-unresolved isn’t the kind of rule that belongs in a linting config, because it makes a lot of assumptions about how modules are resolved, leading to false positives in many common cases. For example in Webpack, the use of aliases or non-traditional but registered extensions such as .vue will raise a linting error when Webpack actually has no problems resolving these files.

[jimbolla]

There’s a webpack resolver for eslint-plugin-import that handles things like extensions and aliases.

[chrisvfritz]

Hmm… this plugin is definitely the only other tool that I’ve had to configure - even on large projects with very demanding build processes. So it does seem strange to have to duplicate that config, especially because it comes with no advantages I can see. Webpack and other build tools already provide very helpful module resolution errors (on save with a dev server) and never trigger false positives. 😕

As someone who maintains a project generator for thousands of other developers, this is the only Airbnb rule I’ve had to disable completely - and it was in direct response to people opening issues about the confusing errors they get from ESLint when using Webpack aliases.

It seems clear this is a wontfix though, so I’ll drop it.