vitest-auto-spy 5.2.0 → 5.3.0

package/AGENTS.md

@@ -2485,17 +2485,24 @@ blanket downgrade so those keep their severity; do not copy the two names into a
 | `no-dead-schemas`                 | `error` | —                 | `schemas` on a testing module with no `declarations` — the schema applies to nothing; the file decides, so a `declarations` in another `configureTestingModule` call silences it |
 | `no-import-time-spread`           | `error` | suggest           | `export const x = [...Imported]` at module scope → a `TypeError` while the bundle loads                                                   |
 | `no-unregistered-inject-spy`      | `error` | —                 | `injectSpy(X)` for a token this file never registered → the real instance, whose spy helpers exist only for the compiler                  |
-| `prefer-render-shallow`           | `error` | suggest           | `TestBed.createComponent` in a file that never reads the template → `renderShallow(X)`; 0.24× the per-test cycle at 100 children          |
+| `prefer-render-shallow`           | `warn`  | suggest           | `TestBed.createComponent` in a file that never reads the template → `renderShallow(X)`; 0.24× the per-test cycle at 100 children          |
 | `prefer-observer-stub`            | `error` | —                 | a hand-rolled observer global → `stubIntersectionObserver()` / `stubResizeObserver()` / `stubMutationObserver()`; the manual save-and-restore goes too, `restoreMockedProps()` runs the undo |
 | `jasmine-namespace-without-entry` | `error` | —                 | `.and` / `.calls` / `.withArgs` on a library spy in a file that installs the compat layer nowhere — option: `{ setupModules: […] }`       |
 | `no-jasmine-globals`              | `error` | —                 | `jasmine.*`, bare `spyOn(` / `spyOnProperty(` / `spyOnAllFunctions(` / `fail(` / `pending(`, `.withContext(`                              |
 | `no-save-arguments-by-value`      | `error` | —                 | `spy.calls.saveArgumentsByValue()` — a no-op here, so the spec silently asserts on post-mutation state                                    |
 | `prefer-native-spy-api`           | `error` | `--fix` / suggest | `.and` / `.calls` where the spy's own API says the same thing — turn it on for the last mile off the jasmine shim                         |
 
-Twenty-three rules, **every one an `error` since 4.0.0**; three fix on their own, eight offer
-suggestions. Twenty-two are syntactic; `no-private-member-access` is the one that reads types, and it
-reports nothing at all without `parserOptions.project` / `projectService` rather than guessing. The config used to be a graded mix of `error` / `warn` / `off`, which decided for the
-consumer how much each finding mattered — a `warn` nothing reads is `off` with extra output. Three of
+Twenty-three rules, **every one an `error` since 4.0.0 except `prefer-render-shallow`**; three fix on
+their own, eight offer suggestions. Twenty-two are syntactic; `no-private-member-access` is the one
+that reads types, and it reports nothing at all without `parserOptions.project` / `projectService`
+rather than guessing. The config used to be a graded mix of `error` / `warn` / `off`, which decided for the
+consumer how much each finding mattered — a `warn` nothing reads is `off` with extra output. The one
+`warn` left is not a judgement about how much that finding matters but about what kind of finding it
+is: every other rule names something wrong or dead, while `prefer-render-shallow` names a file that
+could render more cheaply, and `renderShallow` is a migration a suite either takes or does not. At
+`error` the plugin would gate that migration — 491 findings across 398 of one consumer's 1759 spec
+files — so `recommended` would exist to be overridden. Set it to `'error'` once the project has decided
+to make the move. Three of
 them can report on a _correct_ project, and only one has an option:
 `jasmine-namespace-without-entry` takes `['error', { setupModules: ['./test-setup'] }]`, naming the
 file where `enableJasmineCompat()` is called; `prefer-native-spy-api` goes `'off'` for as long as a

package/README.md

@@ -3026,11 +3026,11 @@ import autoSpy from 'vitest-auto-spy/eslint-plugin';
 export default [{ files: ['**/*.spec.ts'], ...autoSpy.configs.recommended }];
 ```
 
-**Every rule is an `error` since 4.0.0.** The config used to grade them `error` / `warn` / `off`,
-which chose for you how much each finding mattered; a `warn` in a repository that does not read lint
-output is `off` with extra noise, and which findings block a merge is one line of config either way.
-To turn one down, spread the rule map as well — a bare `rules` key beside the spread config replaces
-it rather than merging, silently:
+**Every rule is an `error` since 4.0.0, bar one.** The config used to grade them `error` / `warn` /
+`off`, which chose for you how much each finding mattered; a `warn` in a repository that does not read
+lint output is `off` with extra noise, and which findings block a merge is one line of config either
+way. To turn one down, spread the rule map as well — a bare `rules` key beside the spread config
+replaces it rather than merging, silently:
 
 ```js
 export default [
@@ -3042,6 +3042,16 @@ export default [
 ];
 ```
 
+The one exception is `prefer-render-shallow`, which ships as a **`warn`**, and the reason is the kind
+of thing it says rather than how much it matters. Every other rule here names something wrong or dead
+— a double that drifts from its class, an assertion that never runs, a provider the container already
+dropped, a schema guarding nothing. That one names a file that could render more cheaply, which is a
+choice a suite makes and not a defect in the file: moving onto `renderShallow` is a migration a
+project either takes or does not, and at `error` the plugin would be gating it. On the 1759-file suite
+it was measured against the rule reports 491 times across 398 files — a first run every consumer would
+have to answer with a project-wide `warn` of its own. A project that has decided to make the move sets
+it to `'error'` in the same one line that turns the others down.
+
 A second config, `autoSpy.configs.typeErrors`, holds the subset whose findings are compile errors
 (`prefer-as-spy` is `TS2352`, `no-mocked-for-spy` is `TS2322`). Spread it **after** a blanket
 downgrade so those keep their severity — the recipe is a spread rather than rule names copied into
@@ -3075,7 +3085,7 @@ export can never be.
 | `no-dead-schemas`                 |   `error`   | —                 | `schemas` on a testing module that declares nothing — a charm protecting nobody, and one that starts working the day `declarations` arrive                                                                            |
 | `no-import-time-spread`           |   `error`   | suggest           | `export const x = [...Imported]` at module scope → a `TypeError` while the bundle loads                                                    |
 | `no-unregistered-inject-spy`      |   `error`   | —                 | `injectSpy(X)` for a token this file never registered → the real instance, whose spy helpers exist only for the compiler                   |
-| `prefer-render-shallow`           |   `error`   | suggest           | `TestBed.createComponent` in a file that never reads the template → `renderShallow(X)`; 0.24× the per-test cycle at 100 children           |
+| `prefer-render-shallow`           |   `warn`    | suggest           | `TestBed.createComponent` in a file that never reads the template → `renderShallow(X)`; 0.24× the per-test cycle at 100 children           |
 | `prefer-observer-stub`            |   `error`   | —                 | a hand-rolled `IntersectionObserver` / `ResizeObserver` / `MutationObserver` written into a global → `stubIntersectionObserver()` and friends, whose undo `restoreMockedProps()` already runs                        |
 | `jasmine-namespace-without-entry` |   `error`   | —                 | `.and` / `.calls` / `.withArgs` on a library spy in a file that installs the compatibility layer nowhere                                   |
 | `no-jasmine-globals`              |   `error`   | —                 | `jasmine.*`, `spyOn(` / `spyOnProperty(` / `spyOnAllFunctions(` / `fail(` / `pending(`, `.withContext(` — none of them exist under Vitest  |

package/dist/cli.js

@@ -2421,7 +2421,7 @@ function checkForeignPragma(graph) {
 }
 
 // src/cli/checks/export-map.generated.ts
-var EXPORT_MAP_VERSION = "5.2.0";
+var EXPORT_MAP_VERSION = "5.3.0";
 var ENTRY_SPECIFIERS = "vitest-auto-spy vitest-auto-spy/bun vitest-auto-spy/bun-angular vitest-auto-spy/node vitest-auto-spy/rstest vitest-auto-spy/rxjs vitest-auto-spy/console vitest-auto-spy/dom-stubs vitest-auto-spy/diagnostics vitest-auto-spy/jasmine vitest-auto-spy/jasmine-compat vitest-auto-spy/observer-spy vitest-auto-spy/angular vitest-auto-spy/angular-http vitest-auto-spy/nestjs vitest-auto-spy/react vitest-auto-spy/vue vitest-auto-spy/svelte vitest-auto-spy/setup vitest-auto-spy/zone vitest-auto-spy/eslint-plugin";
 var EXPORTED_BY = {
   AccessorImplementations: "0 1 2 3 4 12 15 16 17",

package/dist/eslint-plugin.cjs

@@ -1968,7 +1968,7 @@ var recommendedRules = {
   [`${PLUGIN_NAME}/no-dead-schemas`]: "error",
   [`${PLUGIN_NAME}/no-import-time-spread`]: "error",
   [`${PLUGIN_NAME}/no-unregistered-inject-spy`]: "error",
-  [`${PLUGIN_NAME}/prefer-render-shallow`]: "error",
+  [`${PLUGIN_NAME}/prefer-render-shallow`]: "warn",
   [`${PLUGIN_NAME}/prefer-observer-stub`]: "error",
   [`${PLUGIN_NAME}/jasmine-namespace-without-entry`]: "error",
   [`${PLUGIN_NAME}/no-jasmine-globals`]: "error",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vitest-auto-spy",
-  "version": "5.2.0",
+  "version": "5.3.0",
   "description": "Auto-generate fully-typed test spies from a class — across Vitest, Bun, node:test and Rstest, with Angular/NestJS/React/Vue/Svelte recipes. Drop-in replacement for jest-auto-spies and jasmine-auto-spies.",
   "keywords": [
     "auto-mock",

package/skills/vitest-auto-spy/SKILL.md

@@ -370,8 +370,14 @@ forgot one is silent about it.
 
 Four of those rules are for a suite mid-migration off `jasmine-auto-spies`:
 `jasmine-namespace-without-entry`, `no-jasmine-globals`, `no-save-arguments-by-value`, and
-`prefer-native-spy-api` — the last one is **`off`** in the recommended config on purpose, because it
-reports working code. Turn it on for the last mile, once the suite is green, and not before.
+`prefer-native-spy-api` — the last one ships at `error` like the rest, and it is the one rule to set
+to **`'off'`** yourself while the migration lasts, because it reports working bridge code. Turn it
+back on for the last mile, once the suite is green, and not before.
+
+**`prefer-render-shallow` is the only `warn` in `recommended`**, and the reason is what it reports:
+every other rule names something wrong or dead, while this one names a spec that could render more
+cheaply. Moving onto `renderShallow` is a suite's decision, not a repair, so it shows up in the output
+without holding a build — set it to `'error'` once the project has taken that decision.
 
 `doctor` is read-only. It reports what neither the runner nor the compiler can: a `tsconfig`
 `include` pattern that matches no file, a production module importing a spec, a spec importing