Separate rules package

[nstepien]

Yo, I think this package has interesting original rules, but it's packed together with a lot of other eslint plugins which I either have no use for in my projects I work on, or already have configured to my liking, and at a different version.
It would be nice the original rules in a standalone plugin, and have the configs in a separate package. WDYT?

[kitfit-dave]

I would really appreciate this, I only want the rules not the configs, and the plugins (vue) are behind on their eslint dep so I get warnings.

[brettz9]

Besides the other rationales mentioned, while it is helpful to get all of the rules in one config, it can be difficult to override config that has been set for rules in other namespaces (or in the eslint default namespace).

For example, your base rules include no-console set to a warning, so if I include one of your configs in my overrides (so as to get all yourcustom rules without having to manually specify them), the no-console rule I have in my main rules will get overridden (there is no way for me to specify priority of my rules within overrides unless I manually add back my config on top of yours).

[MichaelDeBoey]

Hi @nstepien!

Since this repo is unmaintained, you might want to re-open this issue in the @eslint-community fork https://github.com/eslint-community/eslint-plugin-mysticatea

For more info about why we created this organization, you can read https://eslint.org/blog/2023/03/announcing-eslint-community-org