lint-suite 2.0.1 → 2.1.0

package/README.md

@@ -44,6 +44,9 @@ import { recommended } from 'lint-suite/eslint';
 export default [...recommended];
 ```
 
+The package ships as ESM only. A CommonJS config (`eslint.config.cjs`) can
+still `require('lint-suite/eslint')` on Node 20.19+ / 22.12+.
+
 Or selectively include configurations:
 
 ```js
@@ -110,8 +113,9 @@ export default [
 
 `no-unstyled-classes`, `no-unused-classes`, and `no-unused-instance-fields`
 parse component metadata, stylesheets, and templates once per file and keep
-the result in memory for the life of the process, keyed by the file's mtime
-and size. The same entries are mirrored to
+the result in memory for the life of the process, keyed by the installed
+lint-suite version and the file's mtime and size, so an upgrade reparses
+every file. The same entries are mirrored to
 `node_modules/.cache/lint-suite/*.json` under the current working directory
 at process exit, so the next ESLint or stylelint process (a CI run, or an
 editor's first lint) skips every parse of a file that did not change. Set
@@ -170,13 +174,20 @@ templates can read a component or directive member:
   folder, are re-read on every lint; edits to templates in other folders are
   picked up on a throttled schedule (at most every 100× the duration of the
   last check), so a cross-folder template edit can take a moment to show up
-  in another file's diagnostics.
+  in another file's diagnostics. A `templateUrl` file that does not exist
+  yet is remembered as missing and read on the same schedule once it does.
 - `analysis` defaults to `'local'`. Project mode excludes spec-file reads. A
   file it cannot index exactly (a template that does not parse, metadata it
   cannot evaluate, a read it cannot type) falls back to name matching for
   that file only: every member whose name that file mentions counts as read.
   Set `LINT_SUITE_DEBUG=1` to print which files fell back and why, for
   example `LINT_SUITE_DEBUG=1 eslint --no-cache src/app/some.component.ts`.
+- A file with an import that resolves to no module (its file does not exist
+  yet, or is still empty) reads through untyped values, so every candidate
+  member it mentions counts as read, and it is re-indexed on every Program
+  until the import resolves. The project service of typescript-eslint never
+  retries a resolution that failed, so in an editor this lasts until the
+  importing file is edited or ESLint restarts.
 - `allowEffectFields` defaults to `false`. When enabled, fields holding
   auto-cleaned Angular `effect()` calls are allowed; effects configured with
   `manualCleanup: true` must still be read.
@@ -207,7 +218,9 @@ literal class names inside `[class]="..."` expressions and `class="a {{ b }}"`
 interpolations. String literals, object-literal keys, array elements, and both
 branches of a ternary contribute names; identifiers, calls, pipes, and `+`
 concatenations contribute nothing, so a class the rule cannot see is never
-reported. `[ngClass]` is deliberately not analysed.
+reported. `[ngClass]` is deliberately not analysed. `routerLinkActive`,
+`animate.enter`, and `animate.leave` are also read as class lists, static or
+bound.
 
 Stylesheets come from the component beside the template: `styleUrl`,
 `styleUrls`, and inline `styles` read as string or template literals from the
@@ -278,13 +291,17 @@ Selectors resolve through the same parser as the ESLint rule, so `&__element`,
 `&--modifier`, `&.other`, `& > .child`, `.wrapper &`, `@media` blocks, and
 selector lists all report the resolved name on the rule that declares it: in
 `.panel { .inner {} }` only `inner` is checked on the inner rule, never `panel`
-twice. Arguments of `:host(.dark)` and `:host-context(.rtl)` are skipped, and
+twice. A rule that only wraps nested rules, like `.dialog` in
+`.dialog { &__name {} }`, emits no selector of its own and is never reported;
+`.shell` in `.shell { .inner {} }` still is, because `.shell .inner` reaches
+the output. Arguments of `:host(.dark)` and `:host-context(.rtl)` are skipped, and
 everything after `::ng-deep`, `/deep/`, or `>>>` is skipped too, because those
 classes live in other templates. A selector built with interpolation
 (`.icon-#{$size}`) is never reported, and `@extend .base` counts `base` as
 used.
 
-The template side reads the same sources as `no-unstyled-classes` plus
+The template side reads the same sources as `no-unstyled-classes` (including
+`routerLinkActive`, `animate.enter`, and `animate.leave`, static or bound) plus
 `[ngClass]`, and it does not skip custom elements: a class on
 `<app-child class="foo">` is written by this template, so `.foo` counts as
 used. When any template of the stylesheet holds a class source the rule cannot
@@ -468,7 +485,10 @@ export (values and types) that no other file in the TypeScript program
 imports, and a module that exports names but is never imported at all.
 
 - Source of truth is the program typescript-eslint already built for the
-  type-aware rules: no extra parse, no file enumeration, no filesystem.
+  type-aware rules: no extra parse, no file enumeration. The disk is only
+  asked about a specifier the checker cannot resolve, because the project
+  service of typescript-eslint never retries a failed resolution; such a file
+  is re-read on every Program until the specifier resolves.
 - Per file the rule walks top-level statements, plus every node of a file
   whose text contains `import(`, and caches the result
   on the `ts.SourceFile` object; the project-wide usage map is cached per