@cuppachino/eslint-config

• Extendable... fully customized ESLint configuration

• Optimized... for explosive TypeScript development

• Consistent... comment doc formatting with jsdoc and tsdoc

• Seamless... integration with Prettier

• Granular... keep Prettier and ESLint separate without conflict

Using this package in your project

Install

1pnpm add -D eslint @cuppachino/eslint-config

Create a tsconfig.eslint.json at the root of your project and extend your own tsconfig.json:

1{
2  "extends": "./tsconfig.json",
3  "compilerOptions": {
4    "noEmit": true
5  },
6  "include": [
7    "pkg/",
8    // "src/",
9    //  "./vite.config.ts",
10    // "./apps/*/tsconfig.json"
11  ],
12}

Configure

Create a .eslintrc.cjs file in the root of your project and extend the config:

or .eslintrc.js or .eslintrc.json

1module.exports = {
2  
3  /* 1️⃣ focus eslint to not look outside of your project */
4  root: true, 
5
6  /* 2️⃣ extend your config with the package */
7  extends: ['@cuppachino/eslint-config'], 
8
9  /* 3️⃣ point your own tsconfig(s) */
10  parserOptions: {
11    tsconfigRootDir: __dirname,
12    project: [
13      './tsconfig.eslint.json', // REQUIRED
14      './apps/*/tsconfig.json',
15      './packages/*/tsconfig.json'
16    ]
17  },
18  settings: {
19    'import/resolver': {
20      typescript: {
21        alwaysTryTypes: true,
22        project: [
23          './tsconfig.eslint.json', // REQUIRED
24          './apps/*/tsconfig.json',
25          './packages/*/tsconfig.json'
26        ]
27      }
28    }
29  },
30
31  /* ⭐ Override rules here */
32  rules: {
33    // ...
34  }
35}

If you extend additional configs after @cuppachino/eslint-config, you may introduce conflicts between Prettier and ESLint. You can work around this by always including the config last OR by manually adding the eslint-config-prettier package to your project and adding "prettier" to the end of your extends array.

1// ❌ NOT OK
2extends: [
3  '@cuppachino/eslint-config',
4  'plugin:react/recommended',
5]

1// ✅ OK
2extends: [
3  'plugin:react/recommended',
4  '@cuppachino/eslint-config',
5]

1// ✅ OK
2extends: [
3  '@cuppachino/eslint-config',
4  'plugin:react/recommended',
5  'prettier'
6]

IDE Integration

TypeScript

Make sure to use your workspace's version of TypeScript and your tsconfig.json for type checking!

ESLint

To highlight code quality errors in vscode, you can use dbaeumer.vscode-eslint.

Add the following scripts to your package.json for usage in your pipeline:

1{
2  "scripts": {
3    "lint:check": "eslint",
4    "lint": "eslint --fix"
5  }
6}

Prettier

Follow the setup directions for rvest.vs-code-prettier-eslint. This will allow you to fix linting errors with eslint and format your code with prettier, on save, in one step.

These scripts can be used to format your entire project:

1{
2  "scripts": {
3    "format": "prettier --check .",
4    "format:fix": "prettier --write ."
5  }
6}

Development Cycle

If you have the previously mentioned extensions installed, you should be able to use them during development.

Install Dependencies

This package is managed with PNPM. To get started, run the following commands:

1cd YOUR-eslint-config
2pnpm install

Change, Commit, Merge & Release & Publish

1. After you make changes and save, create a new changeset and follow the cli prompts:

   1cd YOUR-eslint-config
   2pnpm new

2. Push your changes to a new branch and open a PR.

3. Once your PR is merged, changesets will automatically create a new release and publish it to NPM.