Linting uses static analysis to inspect source code against coding conventions and rules. It identifies legal TypeScript or JavaScript that may still cause production problems, such as debugger statements or inconsistent Angular selectors. section 9.3.3 section 9.7
A practical linting workflow includes:
- Fix violations before committing changes to version control, or integrate linting into broader team processes. section 9.3.3
Catching a debugger statement and selector violation
Adding `debugger` to `app.component.ts` produces a `no-debugger` error because it can halt deployed code. Changing the component selector from `app-root` to `approot` produces an Angular selector error because component selectors should use the `app` prefix and kebab-case. The application may build despite the style violation, but the selector must also match the HTML for the application to run as expected.
