Auto-resolve named exports from ES2015 modules

It is a common pattern to have a module that exports multiple things, and possibly no default thing. Example:

export function foo() {
  ...
}

export function bar() {
  ...
}

Now, if I want to use one of these functions, I am left in the dust by import-js. It would be nice if we could resolve these named exports automatically.

[trotzig]

This will be fixed as soon as #365 is merged.

[trotzig]

This is related to #184 and #183. I’ve been thinking about this and I think we could add a cache of some sort to the file system. .import-js.cache.json or something. Depending on how long it takes for this cache file to generate, we can either add an explicit command (e.g. import-js init) or make it a one-time startup thing. And if we’re smart about what we store in this cache, we can probably use a little bit of time on some import calls to check if we need to update the cache.

I have a hard time seeing a solution that doesn’t use a cache.

When you say “it is common”, how common do you mean? I haven’t come across many projects that do that.