Henric Persson

While I personally try to stay away from wildcard imports, I don't see why this couldn't be added to import-js. Since editor plugins are responsible for extracting the variable, you'd...

To create a plugin, there are a few options. The best thing is if the editor already supports plugins written in Ruby. Then you can directly instantiate a `ImportJS::Importer` with...

I've got a lot on my plate right now, so I won't get to this in a while. If anyone is willing to give it a go, here's a good...

It might be possible to avoid the direct dependency on the `node_modules` folder by using `require.resolve` (through our wrapper module `requireResolve`) instead of constructing that path to the package.json ourselves.

> If we were to utilize eslint-import-resolver-webpack (perhaps keyed by and implemented by the inclusion of a webpack environment) to attempt resolution of webpack module-names to a file, would not...

That whole module is causing problems... It's a thing that slides down from the top of the page telling you to install a native iphone app. Not something I'm a...

Yeah, not sure what to do here. Identifying this pattern and putting the imports in a separate block sounds complicated. I think this might be one case where you just...

The first set of errors seems to come from trying to follow a require from inside a node_module dependency. For jest for instance, it has a main file that does...

Lol, I wrote that up a little bit too quickly. It's sort of related to that, but I wonder if we should just check for visibility and ignore if invisible.

This is the snapshot image. It's actually a little taller than what you see in this screenshot.