finding(test-config): two examples/ vite.configs stay outside the invocation guard after objectui#3240 — deliberate, and now the whole of a small gap

[claude]

Found while implementing objectui#3240 (PR #7523). Recording the boundary that change deliberately did not cross, so it is visible rather than inferred.

Vitest loads the config it finds in the directory it was launched from, and its fallback does not stop at vitest.config.* — with none present it uses that directory's vite.config.*. PR #7523 makes every packages/PKG/vite.config.ts call assertCanonicalVitestInvocation (gated on process.env.VITEST, so vite build is never refused), and a pin in scripts/__tests__/vitest-invocation-guard.test.ts keeps it that way.

Two directories are excluded on purpose:

• examples/byo-backend-console/vite.config.ts
• examples/console-starter/vite.config.ts

They are templates a user copies out of the repo. A ../../scripts/vitest-invocation-guard.mjs import would resolve here and break there — in the one place the example is supposed to work.

What that leaves. Neither has a test script or a vitest devDependency, so pnpm --filter ... test and turbo run test cannot reach them. The only route is a hand-typed cd examples/console-starter && pnpm exec vitest run, which would collect examples/console-starter/test/vite-alias-closure.test.ts (1 file, real, and also collected by the root unit project) under a build config with no alias table and no setup, unrefused.

⚠️ This is pre-existing and unchanged by PR #7523 — both directories were on this route before it and after. It is filed because that PR makes the rest of the population uniform, which turns these two from "part of a large gap" into "the whole of a small one", and a small named gap is the kind that stops being noticed.

Not obviously worth fixing; the options all have a cost:

• inline a copy of the guard check in each example (duplicated logic, still breaks nothing when copied out);
• have the examples resolve the guard optionally and no-op when absent (a guard that silently no-ops is its own hazard, and objectui#5406 is about exactly that);
• accept and document (what PR test(repo): one vitest config, one verdict — delete the 17 per-package configs (#3240) #7523 does today, in the guard's docstring).

⛔ No action taken. Filed for triage, not as a defect claim.

---

Generated by Claude Code