noUselessIndex is not applied on project-relative path segments

[park-jemin]

As part of the no-useless-path-segments, we have a noUselessIndex option to remove unnecessary indexes. So the expected behavior works fine on relative imports:

import foo from './foo/index'; // flags fine

But when it comes to references from project-relative imports (e.g., absolute imports in Next), it doesn't seem to get detected:

import foo from 'foo/index'; // does not flag

Should we consider making this its own rule?

[ljharb]

No, I think this is just part of the tradeoff you make by choosing a nonstandard approach - ie, project-relative imports.

There's no reasonable and reliable way for static analysis to "just know" that bare specifier aliases reliably point to what should be relative file paths.

[park-jemin]

Can you elaborate how that would affect detecting unnecessary index or index.js file imports in the path? Not sure I'm getting what you mean

[ljharb]

A bare specifier typically maps to a package, and packages might have "exports", which wouldn't work with this rule.