Henric Persson

I understand the issue. Having an `includes` config option which would allow sibling projects to be searched could be a little tricky because the file watcher we use (watchman) needs...

I guess that would work given that we document it properly with the potential addition of `includes`.

Interesting, thanks for trying it out. I recently worked in a project which made use of Lerna (https://github.com/lerna/lerna) and import-js was able to resolve imports across sibling packages. And if...

Import-js currently doesn't support imports using `*`. Supporting it makes sense, although I question if your second example is a good idea - I think it's better to use ```js...

`moduleNameFormatter` can only transform the path to the module your importing. In your case, `./actions'. Which won't get you far in this case. I'll keep this in mind when iterating...

I see, thanks for providing that example. The first thing we can do is to make import-js recognize these as imports, so that it doesn't move them out of the...

I just released 2.0 with a fix for this issue. We still don't produce these import statement types, but import-js will at least recognize them as proper imports. https://github.com/Galooshi/import-js/releases/tag/v2.0.0

@dcporter asked in #385 how I would implement support for producing these, and I wanted to share some of my thoughts here. First of all, just to make sure I...

By match, I mean given a word your cursor is currently on (when using "import word under cursor") or an undefined variable (when using "fix all imports"). Here's an example...

Reopening sounds like a good plan. I have the same FUD, but it might just be one of those things you have to write down in code once before it...