Skip to main content

📚 FAQ

Why you didn’t include ESLint plugins/rules for "X" library?​

  • Cypress ➜ Don't use Cypress. Use Playwright instead.
  • Testing library ➜ I believe Sheriff should not encourage wrong testing practices. In my opinion testing library is one of the least efficient ways to test UIs, by priciples. In most codebases it does more harm than good. You can use Storybook to test components in isolation and Playwright for any kind of integration and end-to-end tests.

Is Sheriff compatible with "X"?​

  • Vite ➜ Yes.

  • Next.js ➜ Yes. Sheriff has explicit support for Next.js. You can enable it in the Sheriff config options.

  • CRA ➜ Yes. Just add this line to your .env file:

    .env
    DISABLE_ESLINT_PLUGIN=true

  • Rome ➜ No. Rome is not compatible with ESLint in the first place.

  • Deno ➜ No. Deno is not compatible with ESLint in the first place.

  • Bun ➜ Untested.

Does Sheriff support vanilla Javascript codebases?​

Sheriff is a Typescript-first ESLint configuration. It's focused on Typescript codebases. You can almost consider Sheriff a superset of @typescript-eslint.
If your codebase is not written in Typescript, you should would worry about that first, before worrying about linting.

For this reason, vanilla Javascript is not supported as of right now, but support may come at a later time.