import-js / import-js/eslint-plugin-import

import/no-unresolved can't detect the root package

Open
#3,082 1 comment 0 reactions 0 assignees View on GitHub
`exports` support
Dominant language
JavaScript
Stars
5.9k
Forks
1.5k
PR merge metrics
No merged PRs in 30d

Description

Node.js can do this:

```js
// in package foo, in test script:
import foo from "foo"; // import itself for test!
```

It seems import/no-unresolved can't handle this.

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the package self-import example with the import/no-unresolved rule in a Node.js package, then trace the rule's module-resolution entry point. Done means the package's own import is accepted while genuinely unresolved imports are still reported.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js
Domain
tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.