@angular-eslint/template-parser

This parser does exactly what it promises: transforms Angular templates into an ESLint-compatible AST. In production builds, it's essentially a dev-time dependency with zero runtime impact, which is exactly what you want. The parser integrates cleanly with ESLint's existing infrastructure and handles inline templates and separate HTML files without special configuration.

From an operational perspective, it's refreshingly low-maintenance. Parse errors are clear and actionable, pointing to specific line/column positions in templates. Memory usage stays reasonable even on large monorepos with hundreds of components. The parser doesn't introduce connection pooling or retry logic because it's a synchronous, stateless operation—parsing happens during lint runs with predictable performance characteristics.

The main gotcha is version alignment: you must keep @angular-eslint/template-parser synchronized with your Angular version and the rest of the @angular-eslint ecosystem. Mismatched versions lead to cryptic parse failures. Documentation around configuration options is sparse, though most projects won't need custom parser options beyond what the preset rules provide.

This parser is the backbone of ESLint support for Angular templates and works seamlessly within the @angular-eslint ecosystem. In daily use, it quietly does its job—parsing .html template files so ESLint rules can analyze them. The TypeScript types are well-defined, making it straightforward to extend with custom rules if needed.

The integration with Angular's template syntax is comprehensive, handling structural directives, property bindings, event bindings, and template reference variables correctly. Error messages are generally clear when parsing fails, typically pointing to malformed template syntax. The parser correctly handles both inline and external templates, which is critical for real Angular projects.

The main friction point is that it's essentially a required infrastructure piece rather than something you interact with directly—you install it as part of angular-eslint setup and rarely think about it again. Documentation assumes familiarity with ESLint's parser architecture, which can be opaque for developers trying to debug unusual template linting issues or write custom rules.

This package is the backbone of ESLint support for Angular templates, and if you're building Angular apps with ESLint, you'll need it. The integration with @angular-eslint/eslint-plugin works smoothly once configured, and it correctly parses Angular template syntax including structural directives, template variables, and expressions. The parser handles complex scenarios like nested components and pipe chains reliably.

The learning curve can be steep initially because you're dealing with multiple moving parts: the parser, the plugin, and ESLint configuration. Documentation in the main angular-eslint repository is decent, with migration guides from TSLint being particularly helpful. Error messages when rules are violated are generally clear, though parser errors themselves can sometimes be cryptic if you have malformed templates.

Day-to-day usage is mostly transparent - you configure it once and forget about it. Debugging linting issues occasionally requires diving into the AST structure, which isn't well-documented. The package updates frequently with Angular releases, which is good for compatibility but means staying on top of breaking changes.