Joe Lencioni

I think the first step would be for this plugin to catch on. Then, when a bunch of people are using it, we can add this feature and hope that...

Regarding [the `@exports` comments you suggested](https://github.com/trotzig/import-js/issues/135#issuecomment-172649132), I think that since the ESM syntax supports what we would need out of the box that we should at least start by only...

I've been thinking about this some more and I think that each project's package.json is a good spot for something like this. Here's a proposal. What if we looked in...

I think maybe we should allow packages to specify an array of entry points, and then auto-resolve the named exports (#199) from the main file and the other entry points....

I won't be able to get to it soon, so you'll probably beat me to it. Are you planning on using regex or AST parsing? If you go down the...

I've been thinking about this some more and I've thought of a couple tricky things that need to be kept in mind. If we are trying to determine what named...

Yeah, I think we need to look at the files in each of the top-level dependencies. I'm a little worried about relevance, of the results, but maybe it will be...

I think we need to include files in packages when matching, so I've opened #344 to track that. We can discuss and improve ranking of matches separately here.

[2.5.0](https://github.com/Galooshi/import-js/releases/tag/v2.5.0) included a change that sorts the unresolved imports by path distance to the current file. I think there's more that we could do here, but this seems like a...

@coaxial I'd be happy to review a pull request that adds this feature and tests. I think you'd probably need to modify something around this area: https://github.com/Galooshi/import-js/blob/6e88abfe80ffc904363250a95b5ef8afc15b89b5/lib/findExports.js#L94-L108