Henric Persson

What if instead of `allowInternalModulesFor`, we had a `includes`? It overwrites whatever is defined in `excludes`, and then you can do things like: ``` excludes: [ './**/build/**', ], includes: [...

Yeah, that would be an issue. I guess the naive answer is to give `includes` precedence, and document that in the README. I could see this adding confusion though, and...

Thanks for the report! That does indeed look like a bug. I'd be happy to review a PR fixing things if anyone has the bandwidth to take it on.

I agree that the current behavior is a little inflexible. Can you explain what you want the imports to look like? We've discussed making the groups configurable in the past...

Thanks for providing that context. I agree that it's a little odd to have both those configuration options. I think the reason is that they were added one by one...

I like this idea!

Hi @mattnibs! This library is not under active development right now, we've been busy with other things. But it's still a tool I use daily while writing code. We haven't...

Hi @justincampbell, thanks for giving import-js a spin! I have limited ember experience, so I played around with a fresh project to better understand the issues you are facing. I...

> That would be great! What about the namedExports though? Won't that be removed eventually? I'm pretty sure they'll stick around for now at least. The reason we deprecated them...

> Also regarding the config file, @alisdair pointed out to me that maybe we could use https://github.com/ember-cli/ember-rfc176-data to generate the aliases and namedExports. Good call. I'm looking into an automatic...