Skip to main content
ember-template-lint is a linter for Ember and Glimmer Handlebars (.hbs) template files. It checks for accessibility violations, deprecated patterns, template anti-patterns, and style issues in Ember.js and Glimmer templates. CodeRabbit runs ember-template-lint v7.9.4.

​
Files

ember-template-lint considers files with the following extensions:
  • .hbs

​
Project detection

CodeRabbit runs ember-template-lint only when changed .hbs files appear to belong to an Ember project. A pull request is treated as Ember-related when at least one of these signals is present:
  • A changed .hbs file is under a standard Ember template or component path, such as app/templates/, app/components/, addon/templates/, addon/components/, or tests/dummy/app/.
  • The repository contains an Ember project marker, such as .ember-cli, ember-cli-build.js, ember-cli-build.cjs, or ember-cli-build.mjs.
  • A nearby package.json or the repository-root package.json includes Ember dependencies, such as packages named ember, ember-*, or @ember/*.
This avoids running ember-template-lint on unrelated Handlebars files, such as generator templates, when the repository does not contain Ember project signals.

​
Configuration

​
boolean
default:true
Enable ember-template-lint
.coderabbit.yaml
CodeRabbit searches your repository recursively for .template-lintrc.json, excluding CI configuration paths. This is the only supported configuration file. .template-lintrc.mjs, .template-lintrc.yaml, and .template-lintrc.yml are not loaded. When no JSON configuration is found, CodeRabbit generates fallback rules based on the selected profile:
  • Chill checks security issues, definite bugs, and critical accessibility violations.
  • Assertive includes the Chill rules and adds broader accessibility, deprecation, and best-practice checks.
Repository JSON configurations supply their own rules in both profiles, including rules that report warnings. CodeRabbit filters no-bare-strings and require-button-type diagnostics in both profiles. CodeRabbit runs the sandbox-installed linter without installing project packages or plugins. Inline configuration is disabled with --no-inline-config.

​
When CodeRabbit skips ember-template-lint

CodeRabbit skips ember-template-lint when:
  • No .hbs files are present in the pull request diff.
  • Changed .hbs files are not under standard Ember template paths and CodeRabbit cannot find Ember project markers or Ember dependencies nearby.
  • ember-template-lint is detected in GitHub Actions, GitLab CI, CircleCI, or Azure Pipelines YAML configuration.
  • CodeRabbit finds .template-lintrc.js or .template-lintrc.cjs, even when .template-lintrc.json also exists, because these configurations can execute code.
  • The repository JSON configuration contains a top-level plugins or extends key, even if its value is empty, because these keys can load external code.
  • The .template-lintrc.json file cannot be read or parsed.

​
What’s next

All supported tools

Browse the complete list of linters, security analyzers, and CI/CD integrations available in CodeRabbit.

Tools reference

Explore detailed specifications and capabilities of all available CodeRabbit tools.

Configuration reference

Full reference for all available options, including how to enable, disable, and tune individual tools.