Core

[brettz9]

Fixes #21 and #23

• Remove non-core rules (vue, ts, eslint-comments, eslint-plugin, node, prettier)
• Remove all configs except as needed to cover project-defined rules
• Linting as per latest prettier
• Testing: Change from broken use of "category" to relying on custom meta.version for determination of ES version (eslint docs allowing for customization within meta)
• Testing: improve coverage slightly
• Docs: fix jsdoc description
• Update devDeps

Note that this is not a PR to be accepted here, but a PR to suggest a separate repository, @mysticatea/eslint-plugin-core (or however you'd want to name it). That is why I've submitted it as a draft, but it should be ready for review.

If you are amenable to setting up such a separate repository, e.g., with the contents of this PR, I could look to amending the current code of @mysticatea/eslint-plugin proper to make use of this proposed @mysticatea/eslint-plugin-core project.

[brettz9]

Btw, while there were some other aspects of your config which might be of general interest, such as:

• Combining globals with ecmaVersion
• Defaults for config files
• Disabling of certain CJS globals in modules
• Expanding of node plugin's tryExtensions

...I didn't add these as:

1. I thought this proposed core package should be granular in being focused on rules.
2. I thought they could be added to their own separate package if desired (and are not too difficult to add manually in any case), allowing those who didn't want your custom rules for some reason or other to also benefit from them.

[brettz9]

@mysticatea : Hi... Was just wondering if you were open in principle to this concept of a separate core plugin having the custom rules only (also asked for in #23) from which @mysticatea/eslint-plugin could derive? If not, I suppose I could just publish this myself, but it'd be nice to get the benefit of any new rules you might wish to add in the future if you were open to maintaining it. Thanks!

[brettz9]

I've published my own @brettz9/eslint-plugin which just extracts the bare rules (and the es5 and es6 configs), so if you aren't planning on developing this further on your own, you're of course welcome to close.