ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #eslint
In a large monorepo, a single ESLint config can’t satisfy every package. ESLint’s "overrides" let you tailor rules per package or language, keeping a single config file while avoiding false positives. This guide shows how, with a concrete example, the trade‑offs, and best‑practice actions.
Stop relying on documentation to maintain project architecture. Learn how to write custom ESLint rules using AST visitors to programmatically enforce boundary constraints.
Use ESLint’s <code>overrides</code> to let <code>console.log</code> in test files while keeping <code>no-console</code> for production code. A practical config, run‑time verification, and common pitfalls are covered.
Make Prettier the sole formatter and ESLint the linter in WebStorm, orchestrated via Actions on Save. Use project-root .prettierrc and .eslintrc for team consistency and verify with intentional formatting and lint errors.
Learn how to build and implement custom ESLint rules using the AST to enforce project-specific architectural patterns and automate code migrations.
When using ESLint to automatically apply fixes, a custom rule that transforms source code may be invoked multiple times during a retry loop. Each invocation writes the same transformed content back to the file, resulting in duplicate write operations that clutter the version‑control history and can cause unnecessary rebuilds. The desired outcome is for the f
Configuration Strategy for Monorepo Plugin Loading In ESLint v9.0.0+, the transition to Flat Config (eslint.config.js) replaces the legacy hierarchical .eslintrc system. While Flat Config offers explicit control via the files and ignores arrays, monorepos often face challenges when different packages require varying versions of the same plugin. There is a tr
ESLint rules utilize a synchronous visitor pattern to traverse the AST. When implementing complex static analysis logic within a custom rule, the execution remains on the main event loop, as the engine does not natively support asynchronous visitors or await promises returned by rule functions. For large-scale codebases or rules requiring heavy computational
Goal Determine a clear migration path for projects still using legacy .eslintrc files when upgrading to ESLint 9, given the documented shift to the flat‑config system and the ongoing ambiguity about when legacy support will be removed. Constraints & Uncertainty The flat‑config model replaces the directory‑based cascade of legacy .eslintrc files with an o
javascript
webstorm