import/order: needs a champion?

@jfmengels / @ljharb: what do y’all think of spinning import/order (and maybe more/all the pure style-guide rules) out into a separate plugin?

There is clearly an enthusiastic user base, but I am not a member thereof and so I think it’s frustrating for everyone when I basically just don’t get involved, and I don’t have the bandwidth already to manage the static analysis stuff (which I do use and am passionate about).

Thoughts?

Practically, I think we’d move the current implementation either back to @jfmengels’ project or to some new project (not sure whose, in that case) and then deprecate here with a note to migrate to the new separate plugin, and remove in v3.

[dantman]

I think this idea is worth revisiting.

import/order has not been updated in months and is missing many requested features. Meanwhile import/order has already been forked and that library has already done the work of implementing various feature requests still open in this repo.

It may be worth either deprecating import/order and recommending import-helpers/order-imports instead. Or making it possible for that fork to be merged into eslint-plugin-import and the author to easily improve it.

[benmosher]

that is fair. one of the primary benefits originally was combined exposure of both sides of this plugin. I just hate for the issues to pile up here, is all. I’ve been moving slowly enough as it is on any of the minor bugfixes over the last 12 months or so, I really appreciate all the slack you’ve been taking up.

maybe I’m just mentally overinflated the wave of order issues. will leave it be for now. but yeah, if @jfmengels is done maintaining it (can’t blame him) and I’m not going to really be helpful managing it, that leaves you to champion this rule and its many issues (if you’re up for it) or maybe it’d be good to pull in another primary collaborator from the community.