import/extensions: Requesting the rule treat subpath imports the same as non-package imports

[ajvincent]

• import/extensions documentation
• Subpath imports documentation on NodeJS

I use subpath imports (prefixed with #) in my Motherhen project as a shortcut to import Foo from "../../../../someDir/someOtherDir/Foo.js". The examples for import/extensions, unsurprisingly, don't cover this case. Apparently, the tests don't cover this either.

My preference is to treat subpath imports identically to non-package imports - and to test for the same.

Failing that, I would consider documenting subpath import examples sufficient.

[ljharb]

This plugin uses resolve, which does not yet support exports nor imports (and thus, not subpath imports either).

When it does, we will.

[ajvincent]

Can you point me to a relevant issue link on the resolve package's repository, please, so I may subscribe to it?

[ljharb]

browserify/resolve#222 Is the closest.

[ljharb]

To be clear, i consider the best practice anyways to be keeping a package backwards compatible with pre-exports node - that does, ofc, preclude subpath imports and self-referencing.