import-js/eslint-plugin-import
import/no-unresolved errors if package omits `.js` extension in `main`
Offen
#617 geöffnet am 09.10.2016
bughelp wanted
Repository-Metriken
- Stars
- (5.940 Sterne)
- PR-Merge-Metriken
- (Durchschn. Merge 138T 22h) (3 gemergte PRs in 30 T)
Beschreibung
If a dependency (for instance, a package in node_modules) omits an extension in the main field of its package.json, the import/no-unresolved rule will fail.
For example:
// node_modules/foo/package.json
{
name: "foo",
version: "1.0.0",
main: "index"
}
// node_modules/foo/index.js
const message = 'It is legal to omit a .js on "main" in package.json';
export default message;
// index.js
import foo from 'foo'; // This triggers the import/no-unresolved rule
console.log(foo);
I imagine this should be a simple fix.