vitest-auto-spy 4.5.0 → 4.5.1

package/dist/angular.js

@@ -2526,7 +2526,10 @@ function renderShallow(component, options = {}) {
     imports: standalone ? [component, ...options.imports ?? []] : options.imports ?? [],
     declarations: standalone ? [] : [component],
     providers: options.providers ?? [],
-    schemas: [NO_ERRORS_SCHEMA]
+    // Only where it can do something. A standalone component carries its own dependency scope, so a
+    // module-level schema never reaches its template — and `enableAngularDiagnostics({ deadSchemas })`
+    // is right to report one, which made these two features of the same package cancel each other out.
+    ...standalone ? {} : { schemas: [NO_ERRORS_SCHEMA] }
   });
   TestBed.overrideComponent(component, { set: buildOverride(component, options) });
   options.beforeCreate?.();

package/dist/bun-angular.js

@@ -314,7 +314,10 @@ function renderShallow(component, options = {}) {
     imports: standalone ? [component, ...options.imports ?? []] : options.imports ?? [],
     declarations: standalone ? [] : [component],
     providers: options.providers ?? [],
-    schemas: [NO_ERRORS_SCHEMA]
+    // Only where it can do something. A standalone component carries its own dependency scope, so a
+    // module-level schema never reaches its template — and `enableAngularDiagnostics({ deadSchemas })`
+    // is right to report one, which made these two features of the same package cancel each other out.
+    ...standalone ? {} : { schemas: [NO_ERRORS_SCHEMA] }
   });
   TestBed.overrideComponent(component, { set: buildOverride(component, options) });
   options.beforeCreate?.();

package/dist/cli.js

@@ -2356,7 +2356,7 @@ function checkForeignPragma(graph) {
 }
 
 // src/cli/checks/export-map.generated.ts
-var EXPORT_MAP_VERSION = "4.4.0";
+var EXPORT_MAP_VERSION = "4.5.0";
 var ENTRY_SPECIFIERS = "vitest-auto-spy vitest-auto-spy/bun vitest-auto-spy/bun-angular vitest-auto-spy/node 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 11 14 15 16",

package/dist/eslint-plugin.cjs

@@ -336,6 +336,13 @@ var TEMPLATE_READS = [
 function templatePolicy(context) {
   return Reflect.get(Object(context.options[0]), "templates") === "never" ? "never" : "as-needed";
 }
+var RENDER_MESSAGES = {
+  keepTemplate: '`keepTemplate: true` puts the real template back, and this project set `{ templates: "never" }`. Drop it \u2014 or, when the component genuinely reads its own template through `viewChild` or content projection, silence this line, because the alternative is a spec that cannot reach the component at all.',
+  preferRenderShallow: "`TestBed.createComponent` pays for compiling the template and instantiating the whole child subtree, and nothing in this file reads either \u2014 no `nativeElement`, no `debugElement`, no `By.css`, no `querySelector`. `renderShallow(X)` brings the same component up through the same `TestBed` with the children dropped and the template blank, and leaves inputs, signals, lifecycle hooks and DI exactly where they were; `fixture` is still a real `ComponentFixture`. What it buys is measured in `bench-angular/`: **0.24\xD7** the per-test cycle at 100 children and **0.05\xD7** at 400 \u2014 but at **zero** children the two are level (measurements straddle 1.0, and it is the noisiest row in the benchmark), so a leaf component gains nothing and this report is worth ignoring there. Reach for `{ keepTemplate: true }` when the component reads its own template through `viewChild` or content projection, which this rule cannot see from the spec."
+};
+function buildsDirectiveHarness(source) {
+  return source.includes("createDirectiveHost");
+}
 function readsRenderedTemplate(source) {
   return TEMPLATE_READS.some((member) => source.includes(member));
 }
@@ -1656,13 +1663,11 @@ var preferRenderShallow = defineRule({
   description: "Render through renderShallow() when the spec never reads the rendered template",
   hasSuggestions: true,
   schema: [{ type: "object", properties: { templates: { enum: ["as-needed", "never"] } }, additionalProperties: false }],
-  messages: {
-    keepTemplate: '`keepTemplate: true` puts the real template back, and this project set `{ templates: "never" }`. Drop it \u2014 or, when the component genuinely reads its own template through `viewChild` or content projection, silence this line, because the alternative is a spec that cannot reach the component at all.',
-    preferRenderShallow: "`TestBed.createComponent` pays for compiling the template and instantiating the whole child subtree, and nothing in this file reads either \u2014 no `nativeElement`, no `debugElement`, no `By.css`, no `querySelector`. `renderShallow(X)` brings the same component up through the same `TestBed` with the children dropped and the template blank, and leaves inputs, signals, lifecycle hooks and DI exactly where they were; `fixture` is still a real `ComponentFixture`. What it buys is measured in `bench-angular/`: **0.24\xD7** the per-test cycle at 100 children and **0.05\xD7** at 400 \u2014 but at **zero** children the two are level (measurements straddle 1.0, and it is the noisiest row in the benchmark), so a leaf component gains nothing and this report is worth ignoring there. Reach for `{ keepTemplate: true }` when the component reads its own template through `viewChild` or content projection, which this rule cannot see from the spec."
-  },
+  messages: RENDER_MESSAGES,
   create: (context) => ({
     'CallExpression[callee.object.name="TestBed"][callee.property.name="createComponent"]': (node) => {
-      if (templatePolicy(context) === "as-needed" && readsRenderedTemplate(context.sourceCode.getText())) {
+      const source = context.sourceCode.getText();
+      if (templatePolicy(context) === "as-needed" ? readsRenderedTemplate(source) : buildsDirectiveHarness(source)) {
         return;
       }
       const suggestion = renderShallowSuggestion(context, node);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vitest-auto-spy",
-  "version": "4.5.0",
+  "version": "4.5.1",
   "description": "Auto-generate fully-typed test spies from a class — across Vitest, Bun and node:test, 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

@@ -78,7 +78,7 @@ describe('TaskService', () => {
 
 One `configureTestingModule` per `describe` — reconfiguring per `it()` recompiles the module every
 test. Use `mockReadonlyProp(component, 'selected', signal(true))` for the signals of the class under
-test, `await stable(fixture)` before asserting zoneless state, `renderShallow` for components. For an
+test, `await stable(fixture)` before asserting zoneless state, `renderShallow` for components — `prefer-render-shallow` reports the `TestBed.createComponent` in a file that reads no markup back, and the rewrite is a suggestion rather than a `--fix` because `renderShallow` configures the module itself. For an
 `httpResource()`, `await expectRequest(url).flush(body)` from `vitest-auto-spy/angular-http` is the
 whole dance — the request is issued by `flushEffects()`, not on creation, and the value is settled
 before the promise resolves; by hand it is six steps and asserting early reads the resource's