Split it up/optional dependencies/etc

[lishaduck]

Hello again! How're you doing?

I noticed that remeda got added, yay for fp!
It does bring up something I've been thinking about though, which is that there're a lot of options. By installing sheriff, I install a bunch of plugins for react, astro, jest (and sometimes vitest), etc. I don't mind that much, but it's still a lot. It'd be cool if there was an api kinda like this, I guess:

import { sheriff } from "eslint-config-sheriff";
import { astro } from "@sherifforg/astro";
import { defineFlatConfig } from "eslint-define-config";

export default defineFlatConfig([
  ...sheriff({
    files: ["packages/foo/*.{ts,tsx}"],
    presets: [astro],
    ignores: ["**/*.d.ts"],
  }),
]);

Alternatively, presets were just normal configs, you could do this, though I like the above idea better as the astro preset could be given access the files key, etc, without extra work.

import { sheriff } from "eslint-config-sheriff";
import { sheriffAstro } from "@sherifforg/astro";
import { defineFlatConfig } from "eslint-define-config";

export default defineFlatConfig([
  ...sheriff({
    files: ["packages/foo/*.{ts,tsx}"],
    ignores: ["**/*.d.ts"],
  }),
  ...sheriffAstro(), // Probably needs to passed sheriffOptions?
]);

---

If this is something you'd be interested in, I'd be happy to work on it, as always.
I can't guarantee I'd find time soon, but it's not super important at this point.

[lishaduck]

@AndreaPontrandolfo, is this something you'd be interested in a prototype of?

[AndreaPontrandolfo]

Do you mean something like how Antfu handles it in his config?

[lishaduck]

No. That could also work, but would require installing each plugin manually, when I'd envision you installing a package from sheriff with all the react rules, or all the astro rules, etc.

[AndreaPontrandolfo]

when I'd envision you installing a package from sheriff with all the react rules, or all the astro rules, etc.

Can you expand on what you mean?

[lishaduck]

Say there's a @sherifforg/astro package that depends on the astro lint plugin, parser, etc, then exposes an SheriffPreset[] that's just a function with this signature: (SheriffOptions) => FlatConfig[]. If you need Astro stuff, you'd depend on it and add it to your sheriff config, if you didn't need it, you wouldn't.