eslint
/eslint
Wspiera pracę z ESLint: Flat Config (eslint.config.js), typescript-eslint, własne reguły i automatyczne formatowanie dla jakości kodu JavaScript i TypeScript.
- Autor
- G1Joshi ↗
- Repozytorium
- Agent-Skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 01.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 01.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Wspiera pracę z ESLint: Flat Config (eslint.config.js), typescript-eslint, własne reguły i automatyczne formatowanie dla jakości kodu JavaScript i TypeScript.
Oryginalny opis (EN)
Expert ESLint assistance covering Flat Config (eslint.config.js), typescript-eslint, custom rules, and automated formatting. Use when enforcing code quality and preventing bugs in JavaScript/TypeScript.
Jak działa
- When to Use
- Quick Start
- Core Concepts
- Common Patterns
- Best Practices
- Troubleshooting
- References
Podgląd SKILL.md
---
name: eslint
description: Expert ESLint assistance covering Flat Config (eslint.config.js), typescript-eslint, custom rules, and automated formatting. Use when enforcing code quality and preventing bugs in JavaScript/TypeScript.
---
# ESLint
ESLint is the industry-standard static analysis tool for identifying and fixing problems in JavaScript and TypeScript codebases, configured via modern Flat Config (`eslint.config.js`).
## When to Use
- **Static Code Analysis for JavaScript/TypeScript**: Catching bugs, anti-patterns, and syntax errors before code review.
- **Modern ESLint Flat Config (eslint.config.js)**: Unified, composable configuration format in ESLint v9+.
- **Enforcing TypeScript Best Practices**: Integrating `@typescript-eslint` with type-aware lint rules.
- **Team Code Standardization**: Automating rule compliance across React, Next.js, Vue, and Node.js codebases.
## Quick Start
```javascript
// eslint.config.mjs (Modern Flat Config)
import js from "@eslint/js";
import tseslint from "typescript-eslint";
export default tseslint.config(
js.configs.recommended,
...tseslint.configs.recommended,
{
rules: {
"no-console": "warn",
"@typescript-eslint/no-unused-vars": [
"error",
{ argsIgnorePattern: "^_" },
],
},
},
);
```
## Core Concepts
### Modern Flat Config Architecture (eslint.config.js)
Configuring ESLint v9+ with TypeScript and React:
```javascript
// eslint.config.js
import js from "@eslint/js";
import tseslint from "typescript-eslint";
import reactPlugin from "eslint-plugin-react";
import reactHooksPlugin from "eslint-plugin-react-hooks";
export default tseslint.config(
// Global ignore rules
{ ignores: ["dist/", "build/", "node_modules/", ".next/"] },
// Base recommended JavaScript rules
js.configs.recommended,
// TypeScript recommended with type-checking rules
...tseslint.configs.recommendedTypeChecked,
{
languageOptions: {
parserOptions: {
project: "./tsconfig.json",
tsconfigRootDir: import.meta.dirname,
},
},
},
// React and Hooks rules
{
files: ["**/*.{tsx,jsx}"],
plugins: {
react: reactPlugin,
"react-hooks": reactHooksPlugin,
},
rules: {
...reactHooksPlugin.configs.recommended.rules,
"react/react-in-jsx-scope": "off", // Not needed in React 17+
"@typescript-eslint/no-explicit-any": "error",
"@typescript-eslint/no-unused-vars": [
"error",
{ argsIgnorePattern: "^_" },
],
"no-console": ["warn", { allow: ["warn", "error"] }],
},
},
);
```
### Authoring a Custom Lint Rule
Creating a custom organizational lint rule:
```javascript
// rules/no-hardcoded-api-urls.js
export default {
meta: {
type: "problem",
docs: {
description: "Disallow hardcoded internal API URLs in client code",
},
messages: {
noHardcodedUrl:
"Hardcoded API URL detected. Use environment variables instead.",
},
},
create(context) {
return {
Literal(node) {
if (
typeof node.value === "string" &&
node.value.includes("api.internal.company.com")
) {
context.report({ node, messageId: "noHardcodedUrl" });
}
},
};
},
};
```
### Executing ESLint via CLI
Running analysis and automated fixes:
```bash
# Lint entire repository
npx eslint .
# Automatically fix autofixable problems
npx eslint . --fix
# Lint with caching to speed up recurring runs
npx eslint . --cache --cache-location .eslintcache
```
## Common Patterns
### Strict React Hooks and Accessibility Guardrails
**Problem**: Silent memory leaks and unhandled dependency arrays in React components.
**Solution**:
Configure React and Hooks plugins in Flat Config:
```javascript
import reactHooks from "eslint-plugin-react-hooks";
import jsxA11y from "eslint-plugin-jsx-a11y";
export default [
{
plugins: {
"react-hooks": reactHooks,
"jsx-a11y": jsxA11y,
},
rules: {
...reactHooks.configs.recommended.rules,
"react-hooks/exhaustive-deps": "error",
"jsx-a11y/alt-text": "error",
},
},
];
```
## Best Practices
**Do**:
- Migrate to ESLint Flat Config (`eslint.config.js` / `eslint.config.mjs`); legacy `.eslintrc.*` is deprecated in ESLint v9+.
- Enable `recommendedTypeChecked` from `typescript-eslint` for deep semantic type validation.
- Use `--cache` in CI and local scripts to only lint modified files.
- Ignore files via the top-level `{ ignores: [...] }` object in `eslint.config.js`.
**Don't**:
- Use ESLint for code formatting (indentation, semicolons); delegate formatting to Biome or Prettier.
- Disable rules globally with inline comments (`/* eslint-disable */`); disable specifically with rationale.
- Enable type-aware rules without supplying `parserOptions.project`; it causes parser errors.
## Troubleshooting
| Error | Cause | Solution |
| :-------------------------------------------------- | :--------------------------------------------------------------------------------------- | :-------------------------------------------------------------- |
| `ESLint couldn't find a configuration file` | Project running ESLint v9+ without `eslint.config.js` or `ESLINT_USE_FLAT_CONFIG=false`. | Migrate to Flat Config (`eslint.config.js`) or set legacy flag. |
| `Parsing error: Cannot read file .../tsconfig.json` | `parserOptions.project` path incorrectly configured. | Verify `tsconfig.json` path in `typescript-eslint` config. |
| `Definition for rule '...' was not found` | Plugin imported but missing in `plugins:` object. | Declare plugin name in config `plugins` map. |
## References
- [ESLint Documentation](https://eslint.org/)
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · G1Joshi/Agent-Skills | 100 | MIT |
| TerminalSkills/skills | 100 | Apache-2.0 |
| managedcode/dotnet-skills | 100 | MIT |
| claude-dev-suite/claude-dev-suite | 100 | MIT |
| el-feo/ai-context | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki d4fdbcdd20e7 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100typescript-eslint
Konfiguruje typescript-eslint, wtyczkę ESLint dla TypeScript: reguły świadome typów, no-floating-promises i ustawienia @typescript-eslint. - 100eslint-checker
Uruchamia ESLint do kontroli jakości i stylu kodu JavaScript i TypeScript oraz do analizy statycznej z automatycznymi poprawkami. - 100eslint-biome
Konfiguruje ESLint 9 w trybie flat config i linter Biome: typescript-eslint, kategorie reguł, migrację ze starej konfiguracji i optymalizację wydajności. - 100ts-lint-format
Pomaga wybrać i skonfigurować linter i formater TS: Biome 2.x kontra ESLint 10 z flat config i typescript-eslint. - 100linting-neostandard-eslint9
Konfiguruje ESLint v9 z flat config i neostandard dla projektów JavaScript i TypeScript, w tym migrację z .eslintrc lub pakietu standard oraz integrację z CI. - 95typescript-quality-checker
Sprawdza jakość kodu TypeScript i JavaScript przez ESLint, Prettier, kontrolę typów i analizę bezpieczeństwa.