extensions should ignore imports from packages with invalid names

[novemberborn]

Similar to #340, the extensions rule should ignore imports from packages with invalid names. E.g. files:../../content/**/*.md is not a file path, and not a valid package name.

I suppose this might have to deal with Windows file paths though.

[jfmengels]

Hi @novemberborn :)

Same as #340, do you have an example of a case where this is problematic for you? I'm not sure what kind of problem you're facing here.

[novemberborn]

Sure. I maintain two Babel plugins which rewrite import statements: import-glob and files. An example of the latter is here:

import files from 'files:../../content/**/*.md'

The import isn't a file path (no leading / or disk drive, no leading period), and neither is files:.. a valid package name. Since the extensions rule only deals with file extensions, and this isn't a valid import (because it uses a custom resolver), I don't think the rule should apply.

I suppose this might be solved by writing a resolver for these Babel plugins (though I haven't checked whether this rule follows resolvers). It might be useful for this rule not to result in errors even if there is no custom resolver.

[ljharb]

The proper solution here is indeed to write a resolver.