import/no-unresolved doesnt respect package exports

[thepassle]

If I import something from package foo, that has in it's package.json the following exports map:

"exports": {
  "./bar.js": "./src/bar.js"
}

The following import will cause an import/no-unresolved error, while being completely valid:

import 'foo/bar.js';

[ljharb]

Duplicate of #1810.

[ljharb]

I'd suggest making that package have an actual ./bar.js file, so that pre-exports nodes (and tooling) can locate the file also.

[thepassle]

A better structural fix would be for tooling to catch up with package exports instead

[ljharb]

Both fixes are needed; packages should remain backwards-compatible, instead of being hostile to those users.

Certainly this package, and the ecosystem's tooling, will eventually catch up as well.

[thepassle]

packages should remain backwards-compatible, instead of being hostile to those users

The foo package I mentioned doesnt have this requirement

[ljharb]

I gathered that - I'm saying that all packages should have that requirement.

[thepassle]

I disagree with that, but I guess its besides the point. You mentioned that "eventually" this plugin will support package exports, the issue you linked has been open for 2 years, is there already work started to support package exports? If not, would you be willing to take a PR? I might be able to spend some time and take a stab at it

[ljharb]

The work needs to be done in the resolve package; it has begun and is moving slowly.