Proposal: merge into `eslint-plugin-jsonc`

[JounQin]

In case you are not aware, there is a https://github.com/ota-meshi/eslint-plugin-jsonc built with correct jsonc-eslint-parser, I think we should work together to benefit to the whole community.

cc @ota-meshi

[kellyselden]

Thanks for the suggestion, but closing as I'm not planning on working on this currently.

[JounQin]

I'm not quite sure to understand, in README:

I wouldn't mind getting this merged into eslint-plugin-node or eslint-plugin-json.

I believe eslint-plugin-jsonc is a much better solution for .json files than the above two packages.

[kellyselden]

My apologies! I forgot about that section of the README.

[ota-meshi]

I think it's probably best if all rules are merged into eslint-plugin-package-json.
JoshuaKGoldberg/eslint-plugin-package-json#42

eslint-plugin-package-json uses jsonc-eslint-parser, so it can be used together with eslint-plugin-jsonc.

[JounQin]

json-files aims not only package.json, right?

[ota-meshi]

I think everything except the json-files/validate-schema rule mentions package.json.

An alternative to the json-files/validate-schema rule is eslint-plugin-json-schema-validator, which checks JSON using a JSON schema.

[JounQin]

cc @JoshuaKGoldberg

[JoshuaKGoldberg]

Hiyall! Sure, if anybody wants to use eslint-plugin-package-json for package.json-specific things, that'd be great. I set up a tracking issue on JoshuaKGoldberg/eslint-plugin-package-json#42 with a comparison of all the package.json-oriented rules I could find in the ecosystem. That includes eslint-plugin-json-files. It's on my 2024 agenda to get them all merged into eslint-plugin-package-json.

At any rate, it seems to me that once the package.json-specific rules from this plugin are merged into eslint-plugin-package-json, then yeah, there won't be anything this plugin does that isn't captured elsewhere.