yeah this is just not handled yet - it's not a common case at all.

OOC - how often do you have a dangling import('foo')? They're async imports so it seems weird to have one with no await or .then.
Or was this just something you ran into randomly whilst typing?

(note - adding an await or a .then fixes it because it converts it into an expression the base rule understands)

We use dynamic imports to accomplish code-splitting in webpack and to enable prefetching/preloading via webpack.

To my understanding, the example I gave doesn't need a .then because it is loading an angularjs application, which I guess ends up bootstrapping itself as a sort of side-effect. Another place we use a dangling import() is to load css files via webpack, which we could do with a static import but we wanted to take advantage of the code-splitting and prefetching that comes with the dynamic imports. Obviously, a css file loaded via webpack doesn't need a .then either.

To be honest, I'm not an expert in webpack so maybe these are bad reasons haha, but hopefully that answers your question.

That makes sense yeah.

It wouldn't be a difficult fix if you'd like to give it a go!
I believe all you need to check for and ignore is an ImportExpression.

I've never contributed to an open source project before, but I'd love to take a crack at it.

Unfortunately I won't be able to start for a couple weeks, but if the issue is still open at that point I'll definitely come back to it.