Skip to main content
Frontend Glossary

Frontend engineering · Code quality

Linter

Also called: Lint, Static analysis, ESLint, Biome

Scan code with static rules—without running it—to catch style issues and common bugs early in the editor or CI.

In detail

Linters catch problems you can see without executing: unused vars, bad Hooks deps, banned APIs, inconsistent formatting (some tools format too). This repo's Biome check is in that family.

They don't replace tests or a type system: TypeScript owns types, linters own conventions and a class of bugs, tests own behavior.

After AI edits, get lint/typecheck green before staring at the page—many "runs but violates repo rules" patches die there.

Developer info
Term ID
eng-linter
DOM selectors
No DOM cues. This concept isn't detected directly on a page.
Priority
1 · when several match at the same level, the higher priority wins
Version
v1 · updated Oct 5, 2026