Henric Persson

Thanks @wincent for chiming in. At the moment we're not peeking in to any node modules folders, but we're discussing doing so for the top-level ones (those listed in package.json)....

Interesting. I didn't think it could be used for non-React stuff first, but after looking at it some more it definitely looks doable.

Right now, only the top level exports are found for package dependencies. We've discussed adding support for finding exports within subdirectories of package dependencies, but no code has yet been...

@GCorbel nothing yet. If you wanted to get involved, #344 is a good place to discuss ways to implement this.

Nice! Not that I'm a coffescript user myself, but I'm sure this can help a lot of people out. Just to make sure I understand this right -- this PR...

There are some linting issues. I'll fix those up before I merge this.

I fixed the lints and merged this to the [`coffeescript-support`](https://github.com/Galooshi/import-js/tree/coffeescript-support) branch for now. A pre-release was also shipped that you can install by running `npm install -g import-js@next`. I tried...

Yep, there’s some legacy here for sure. The tool was originally written in Ruby, then ported to javascript. A quick theory that might be worth exploring: when you compile to...

Do things change if you give `export * from 'a'` a relative path? => `export * from './a'`. If that doesn't work, can you see if you can modify this...

Nice! I'm definitely open to reviewing these changes. When you do open a PR, can you make sure to explain each change (why it is needed, trade-offs with your implementation...