Add main to work around eslint-plugin-import issues

[tanhauhau]

No description provided.

[yannbf]

This sounds like a great (and needed) feature! Any chance this could get merged? Thanks!

[benmccann]

import-js/eslint-plugin-import#1810 is still not fixed, but at this point I'm of the opinion that they need to fix their package rather than expecting the entire ecosystem to work around their lack of support for the latest standards. There's been a PR for browserify/resolve#222 open for three years and it's still stuck in limbo. It's getting to be a bit ridiculous

[ljharb]

@benmccann again, i'd appreciate if you avoided hostility, especially when describing unpaid volunteer work that's not proceeding as fast as you'd like.

[benmccann]

I've discovered another solution is that you can also use eslint-import-resolver-exports to configure eslint-plugin-import to correctly handle this case. It's admittedly rather cumbersome to setup, but that's really something that should be addressed in those projects

Another option would be to use tsc rather than eslint-plugin-import. That's what I've done in my own projects as I found that it catches all the same issues