Question 1

How do I migrate from TSLint to Angular ESLint?

Accepted Answer

The project provides a migration guide in the README, detailing steps for Angular CLI projects, including dependency updates and configuration changes to replace Codelyzer and TSLint with ESLint tooling.

Question 2

Angular ESLint vs. plain ESLint: which is better for Angular?

Accepted Answer

Angular ESLint is superior for Angular projects because it includes specialized parsers and rules for Angular templates and TypeScript code, whereas plain ESLint lacks these Angular-specific integrations out of the box.

Question 3

How can I disable a lint rule in an Angular template?

Accepted Answer

Use valid HTML comments with `eslint-disable` syntax, as mentioned in the README, requiring @angular CLI v11.2.8+ and @angular-eslint v2.1.0+ for this feature to work correctly.

Question 4

Does Angular ESLint work well with VSCode?

Accepted Answer

Yes, it integrates with the vscode-eslint extension (v3+), which automatically picks up configuration files, though you may need to adjust settings like `eslint.useFlatConfig` if using eslintrc with ESLint v9.

Question 5

How do I write a custom rule for Angular component templates?

Accepted Answer

Use the @angular-eslint/utils and @angular-eslint/test-utils packages, following the dedicated guide in the README, which covers creating and testing rules for both TypeScript and HTML template ASTs.

Question 6

What's the performance impact of using Angular ESLint on a large app?

Accepted Answer

Performance can degrade with rules requiring type information, as noted in the README, but optimizing configs and avoiding unnecessary rules can help mitigate this trade-off for most projects.

Angular ESLint

What is Angular ESLint?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions