Closed 43081j closed 5 months ago
suggested by @thepassle, it is probably worth providing an open list of alternatives in its own repo. that way, other tools and docs can make use of it, not only the eslint plugin
so it seems we need:
the plugin should really have at least two rules (these can be tracked better in the plugin's repo when it exists):
it'd make sense to start with the native functionality rule since it is well known (e.g. we already know hasOwn
should just be replaced by native hasOwnProperty
)
ill create the org and repo this weekend (knowing we may later rename it or rework it, just a PoC for now)
this has been done
you can find the module replacements here: https://github.com/es-tooling/module-replacements
you can find the eslint plugin here: https://github.com/es-tooling/eslint-plugin-depend/
I already did some of this a few years ago, so we can use it as reference at least: https://github.com/43081j/eslint-plugin-clutter
i would at least rename this as it is not all "clutter"
once we have a community org this stuff can belong to, it should be owned by that
basic requirements of such a plugin: