npm install -D eslint-config-devjskit

The problem

You're a professional, but you're mature enough to know that even professionals can make mistakes and you value your time enough to not want to waste time configuring code quality tools or babysitting them.

This solution

This is a set of configurations you can use in your web projects to avoid wasting time.

Usage

TypeScript

Create a tsconfig.json file in your project root with the following content:

{
  "extends": "eslint-config-devjskit/typescript",
  "include": ["**/*.ts", "**/*.tsx", "**/*.js", "**/*.jsx"]
}

Learn more from the TypeScript docs here.

ESLint

Create a eslint.config.js file in your project root with the following content:

import defaultConfig from "eslint-config-devjskit";

/** @type {import("eslint").Linter.Config} */
export default [...defaultConfig];

Learn more from the Eslint docs here.

There are endless rules we could enable. However, we want to keep our configurations minimal and only enable rules that catch real problems (the kind that are likely to happen). This keeps our linting faster and reduces the number of false positives.

License

MIT