Skip to content

Changelog

What shipped, and what changed.

  1. 0.2.1

    Current package

    • Breaking: check levels are gone. The strict behavior is the default — correctness, security, and accessibility warnings count as errors and style-guide notes count as warnings. The --level flag and the level config key no longer exist. Soften a rule per rule under rules in config.
    • angular-doctor/impure-pipe is now an error, not a warning.
    • angular-doctor/prefer-signal-query is now a warning. It flags each @ViewChild, @ViewChildren, @ContentChild, and @ContentChildren and names the signal query to use instead.
    • Angular 15 or newer is required. Angular 17+ gets every check; Angular 15–16 scan in compat mode, where rules that need newer Angular stay off instead of flagging correct old code. Older versions stop with a clear message.
    • Findings are grouped once per rule in the terminal and in reports. --html also writes a self-contained angular-doctor-report.html with category tabs, a severity filter whose tab counts update live, and reference links that open in a new tab.
    • New rules: inject-async-target (error), prefer-inject-async, template-for-allocation, and getter-in-template (error — a template reading a class getter re-runs it on every change detection cycle).
    • Scans understand multi-project angular.json and Nx workspaces. The DOCUMENT check is a warning when SSR or prerendering is configured.
    • Oxlint runs in the bundled CLI again. Decorated classes are no longer reported as unused exports, --scope changed includes untracked files and scans nothing on a clean tree, report paths are relative, and generated HTML reports are excluded from later scans.
    • Templates are now linted for real: eslint and the Angular template rules ship as dependencies of the engine and run on standalone templates and inline component templates.
    • New check: @defer without an on/when/prefetch trigger is a warning.
    • Docs fixes: page titles reset on client-side navigation via a TitleStrategy, and the rules page "On this page" list follows the severity filter. The rules page groups by category with severity colors and an All/Errors/Warnings/Info filter.
  2. 0.1.2

    Released on npm

    • An error costs 1.5 in each file. A warning still costs 0.75 once per rule. Notes still do not change the score.
    • Oxlint findings keep their rule id and the line they were found on.
    • The landing headline is "Check Angular code." Angular sits on the lamp-red block.
    • The docs pointer is a scan reticle. Clicks land on the red square.
    • Overview commands place the copy control at the right edge of the command.
  3. 0.1.1

    Released on npm

    • Scan .ts and .html only. .js, .mjs, .cjs, and .tsx are no longer read.
    • A check that cannot finish on a file is skipped. The summary names that file, and the rest of the scan still runs.
    • Import text copied from a file is treated as an identifier, so a string that looks like an import no longer stops the run.
  4. 0.1.0

    Released on npm

    • Scan an Angular or Nx project and print a 0–100 health score.
    • Group findings into errors, warnings, and notes.
    • Write an agent-ready Markdown report when the scan is not clean.
    • List and explain rules, and recommend official Angular migrations.
    • Install a starter GitHub Actions workflow.