import-js/eslint-plugin-import

import/no-unresolved errors if package omits `.js` extension in `main`

Open

#617 opened on Oct 9, 2016

View on GitHub
 (2 comments) (1 reaction) (0 assignees)JavaScript (4,946 stars) (1,540 forks)batch import
bughelp wanted

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
toolingdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaScriptESLint plugin basicsNode.js module resolution
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the module resolution logic in the plugin, likely in `lib/core/resolve.js`. Use Node's `require.resolve` or implement fallback for missing extensions in the `main` field. Check existing tests for the `import/no unresolved` rule to ensure no regressions.