ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #eslint
Learn how to configure ESLint's no-unused-vars rule with argsIgnorePattern to ignore underscore-prefixed parameters without weakening the rest of your linting.
Use ESLint's overrides to apply different rule sets to tests, TypeScript, and source files from one config — with correct glob patterns, precedence order, and verification via --print-config.
Learn how to write a custom ESLint rule that blocks imports from forbidden directories, handles relative paths, TypeScript aliases, and flat config, with example tests and performance tips.
Decide how to configure ESLint's no-console rule: compare off/warn/error severities and the allow list, then implement a dev-vs-production setup and verify it fails correctly.
Decide whether to rely on WebStorm’s auto‑fix on save, a pre‑commit hook, or a CI lint step. Compare trade‑offs, see a concrete setup, and validate performance and consistency across editors.
Learn how to replace .eslintrc with eslint.config.js, use JavaScript for conditional rules, and verify your flat config with eslint --print-config.
When ESLint flags console.log statements in production code, the issue usually lies in mis‑configured no-console rules or environment overrides. This guide walks through diagnosing the problem, applying targeted overrides, and verifying the fix so you can keep debug logs without lint errors.
Learn how ESLint overrides let you enforce stricter rules on new or modified files while keeping legacy code tolerant, with a concrete config example and verification steps.
ESLint --fix can clear formatting noise in seconds, but it won't fix unused variables or logic bugs. Here's a safe workflow and the limits to know.
typescript
webstorm
nodejs