Kuidas jälgid sa oma projektis koodistiili järgimist…

To maintain a consistent code style, I use the following tools and processes:

ESLint: I configure code formatting and quality rules (e.g., Airbnb or Standard). ESLint helps identify syntax errors, indentation issues, unused variables, etc.

// Example .eslintrc.js
module.exports = {
  extends: 'airbnb-base', // Or another chosen style
  rules: {
    // Override or add rules
    'semi': ['error', 'always'],
    'quotes': ['error', 'single']
  }
};

Prettier: I integrate Prettier for automatic code formatting. It takes care of spaces, line breaks, semicolons, and other formatting details, working in conjunction with ESLint (via plugins).
```
// Example .prettierrc.json
{
  "semi": true,
  "singleQuote": true,
  "printWidth": 100
}
```

Husky and lint-staged: I set up pre-commit hooks with Husky. Using lint-staged, I run ESLint and Prettier only on changed files. This ensures that only formatted and checked code gets into the repository.

// Example package.json (part)
{
  "husky": {
    "hooks": {
      "pre-commit": "lint-staged"
    }
  },
  "lint-staged": {
    "*.{js,jsx,ts,tsx}": [
      "eslint --fix",
      "prettier --write"
    ],
    "*.{css,scss,less}": [
      "stylelint --fix", // If I use Stylelint
      "prettier --write"
    ],
    "*.{html,vue,svelte}": [
      "prettier --write"
    ]
  }
}

Code reviews: During code review, I pay attention to compliance with established coding style agreements, even if automated tools miss something or there are nuances not covered by rules.
Documentation: I maintain minimal documentation on the adopted code style in the project (e.g., in README or CONTRIBUTING.md), so new team members can quickly familiarize themselves with the rules.
IDE integration: I configure editors (VS Code, WebStorm, etc.) for automatic formatting on save and display ESLint errors directly in the editor.

Kuidas jälgid sa oma projektis koodistiili järgimist?