Currently, import/first seems to require that any import comes before any export, even if the export is an export..from. Reordering them, in this case, could be a potential logic error.

Though, arguably, if the module is capable of exporting, it should also be made side-effect free...

Also related is that import/first does not allow mixing import with export {}, and separating them actually hurts readability.

Consider the following:

// `export * as comment from './comment'` but that is not standard syntax
import * as comment from './comment'
export { comment }

import * as members from './members'
export { members }

The rule will complain about the second import, but moving so all the imports are grouped would actually make it harder to tell they are being reexported.