Relationship to @e18e/eslint-plugin

[tbroyer]

e18e now has published https://github.com/e18e/eslint-plugin which includes a ban-dependencies rule that looks like it duplicates this module.

Can you clarify whether this is the case? and where this plugin is heading? Is it deprecated in favor of e18e/eslint-plugin? Will it be maintained? If it becomes superseded by e18e/eslint-plugin, what's the migration path? (how will projects know about it?)

[43081j]

ultimately this plugin will be absorbed by the e18e plugin, basically.

we haven't yet formed the migration plan. its a simple one, but we need to update docs and what not.

since the rules will all be named the same, its basically a find-and-replace to e18e

this repo doesn't make that clear yet because i wanted to make sure we have the right docs before we make it "official" that this is moving.

any suggestions welcome too, if you have any ideas about how best to migrate

[tbroyer]

Thanks for the quick answer

In terms of migration, I'd like for workflows like npm update, npx npm-check-updates, Renovate, or Dependabot, to warn that this plugin has been superseded by / absorbed into e18&/eslint-plugin.
Adding such a warning to the README and the GitHub release notes should be enough for Renovate and Dependabot, and possibly npm-check-updates for people who go check the update details (IIRC it links to the homepage, which is this repo's README; but for people to have an incentive to go check, maybe the version should be a new major?). For npm update, maybe deprecating the package on the registry would be enough?

…and the warning should link to some migration guide (IMO necessary even if it only says "you have nothing else to do than replace the dependency and update the imports")