Feature: File / path / URL resolving

[GeoffreyBooth]

From an import statement, it is possible for a human to quickly find the file being imported. It doesn’t matter if the module being imported is coming from a local file or a URL.

Use case 13.

[guybedford]

The feature for this could be seen as a "resolver spec" that dev tools can clearly follow (like with Node resolution currently), or it could be seen as a "resolver api".

This didn't seem clear to me that it was referring to a resolver API, so I created a new feature for that that is directly that feature (#157). Then lets let this track its original use case, and mark it as a duplicate of #104.

[demurgos]

From what I remember of the meeting discussions, this issue is specifically for humans working in their editor. This is not about programmatically retrieving the file, but allowing developers to look at a file and then know where to look for the imported file. It may be rephrased as "predictable import locations", "simple import algorithm" or "minimizing the number of indirections". (Avoiding to have to look in 3 config files just to find a dependency).

[guybedford]

@demurgos completely agreed here, but this is still a duplicate of #104 under that interpretation (exactly the same use case number).

[demurgos]

Agreed that both are similar, but I still think they serve a different purpose. I'm neutral on marking it as a duplicate.