@hublo/sentinel 1.4.0-alpha.13 → 1.4.0-alpha.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hublo/sentinel",
-  "version": "1.4.0-alpha.13",
+  "version": "1.4.0-alpha.14",
   "description": "One CLI that guards code health across Hublo repos: shared lint/typescript/build/test presets, static & dynamic analysis, and architecture checks.",
   "type": "module",
   "license": "MIT",
@@ -66,6 +66,10 @@
       "types": "./dist/roles/test/tools/msw.d.ts",
       "import": "./dist/roles/test/tools/msw.js"
     },
+    "./test/tools/mock-extended": {
+      "types": "./dist/roles/test/setup/mock-extended.d.ts",
+      "import": "./dist/roles/test/setup/mock-extended.js"
+    },
     "./test/setup/msw-lifecycle": {
       "types": "./dist/roles/test/setup/msw-lifecycle.d.ts",
       "import": "./dist/roles/test/setup/msw-lifecycle.js"

package/types/mock-extended.d.ts

@@ -5,19 +5,36 @@
  * time a migrated module has ONE copy. TypeScript does not read Vite's aliases, so it keeps
  * resolving the jest package and a migrated spec ends up compiling two worlds at once:
  *
- *     the value    typeof mockDeep<Db>()   -> CalledWithMock<…> extends jest.Mock
+ *     the value    typeof mockDeep<Db>()    -> CalledWithMock<…> extends jest.Mock
  *     the spec     let spy: MockInstance    -> vitest's own type
  *     TS2322       not assignable
  *
  * Measured on `apps/nest/microservices/agency`: one error, on a module whose typecheck was clean
  * before it migrated. 34 files under `libs/` export a type built this way.
  *
- * ## Why here, and not in the module
+ * ## Why it re-exports a SUBPATH of sentinel rather than `vitest-mock-extended`
  *
- * The declaration REPLACES the module's types with whatever it re-exports, so it has to name a
- * package that resolves from wherever the file sits. `vitest-mock-extended` is sentinel's
- * dependency, so a copy of this file placed in an adopting module would resolve nothing and empty
- * the module out: measured, `Module '"jest-mock-extended"' has no exported member 'mockDeep'`.
+ * Because a bare `vitest-mock-extended` does not resolve from here, which was measured with
+ * `--traceResolution` after the first attempt emptied the module out:
+ *
+ *     Resolving module 'vitest-mock-extended' from '…/agency/node_modules/@hublo/sentinel/types/…'
+ *     Module name 'vitest-mock-extended' was not resolved.
+ *
+ * The module's `tsconfig.spec.json` names this file by PATH, so TypeScript keeps the symlink path
+ * pnpm installed and walks up from there: `…/sentinel/node_modules`, then the module's, then the
+ * workspace's. Sentinel's own dependency sits in the store beside its real directory, and none of
+ * those three is it. A file reached by RESOLUTION is realpathed into the store instead, and its
+ * dependencies are found: same trace, `@hublo/sentinel/test/tools/msw` → `msw` resolved.
+ *
+ * `skipLibCheck` is on in every module here, so the failed `export *` was silent and what surfaced
+ * was an empty module: 18 × `Module '"jest-mock-extended"' has no exported member 'mockDeep'`.
+ *
+ * ## Why THIS subpath
+ *
+ * `@hublo/sentinel/test/tools/mock-extended` is the very module the runtime alias points at, so the
+ * types a spec compiles against are the ones it runs against, down to the lifecycle helpers the
+ * fork adds. Re-exporting `vitest-mock-extended` directly would describe something adjacent to what
+ * executes.
  *
  * ## Why it does not couple modules to each other
  *
@@ -31,5 +48,5 @@
  * module at a time; this keeps the test role the same.
  */
 declare module 'jest-mock-extended' {
-  export * from 'vitest-mock-extended'
+  export * from '@hublo/sentinel/test/tools/mock-extended'
 }