[import/no-unresolved] not working for index.js

Repository metrics

Stars

4,946 stars (4,946 stars)

PR merge metrics

Avg merge 138d 22h (Avg merge 138d 22h)3 merged PRs in 30d (3 merged PRs in 30d)

Description

utils/
    index.js
components/
    Foo.jsx
.eslintrc.js
webpack.config.js

export function getPromise () { return 42; }

import { getPromise } from 'utils';

{
  "parser": "babel-eslint",
  "plugins": [
    "import",
  ],
  "settings": {
    "import/resolver": {
      "webpack": {
        "config": path.resolve(__dirname, "webpack.config.js"),
      }
    },
  },
  "rules": {
    "import/no-unresolved": ["error", {commonjs: true, caseSensitive: true}],
    // ...
  }
}

{
  context: root,
  resolve: {
    modules: [root, 'node_modules'],
    extensions: ['.js', '.jsx', '.json', '.coffee', '.cjsx'],
  },
  // ...
}

Contributor guide

Research direction

Investigate the webpack resolver to understand why it fails to resolve module names pointing to index.js files. Check the resolve logic for directory imports.

Tech stack

javascript

Domain

devtools

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.

Active

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

Node.jsJavaScriptwebpack

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

70