📋JSON Templates

.eslintrc.json Configuration

ESLint configuration for JavaScript/TypeScript projects.

Explanation

ESLint config defines code quality rules and linting behavior.

Examples

TypeScript Project Config

Output

{
  "env": {
    "node": true,
    "es2022": true
  },
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/recommended"
  ],
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "ecmaVersion": 2022,
    "sourceType": "module"
  },
  "plugins": [
    "@typescript-eslint"
  ],
  "rules": {
    "no-console": "warn",
    "@typescript-eslint/no-unused-vars": "error",
    "@typescript-eslint/no-explicit-any": "warn",
    "quotes": [
      "error",
      "single"
    ],
    "semi": [
      "error",
      "always"
    ]
  }
}

Code Examples

.eslintrc.json

{
  "env": {
    "browser": true,
    "node": true,
    "es2022": true
  },
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/recommended",
    "prettier"
  ],
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "ecmaVersion": 2022,
    "sourceType": "module"
  },
  "plugins": ["@typescript-eslint"],
  "rules": {
    "no-console": "warn",
    "quotes": ["error", "single"],
    "semi": ["error", "always"]
  },
  "ignorePatterns": ["dist", "node_modules"]
}

Try it Now

Open in JSON Formatter

💡 Tips

Use extends to inherit rule sets
Prettier should be last in extends
Set env for available globals
Use warn for style, error for bugs
Override rules per project needs

⚠️ Common Pitfalls

Conflicting rules between configs
Don't fight with Prettier
Too many rules can slow down linting