@mnemonica/tactica 0.3.12 → 0.4.0

package/README.md

@@ -41,6 +41,8 @@ npm install --save-dev @mnemonica/tactica
 
 `mnemonica` is a peer dependency (>= 1.0.1).
 
+Tactica bundles its own TypeScript compiler (6.x) as a regular dependency, so it installs and runs regardless of the TypeScript version your project uses — including TypeScript 7, whose npm package no longer exposes the classic compiler API. Your `tsconfig.json` is only ever *parsed* (never emitted), so TS5-era options like `baseUrl` keep working even though TS6 marks them deprecated.
+
 ## Usage
 
 ### CLI
@@ -125,7 +127,7 @@ EDS tracking is **auto-enabled** when `@mnemonica/dive` is present in `package.j
 
 ## Generated Files
 
-Tactica writes everything under the `--output` directory (default `.tactica/`):
+Tactica writes everything under the `--output` directory (default `.tactica/`). All file paths inside the JSON files are emitted **project-relative** (anchored at the tsconfig directory) so the output is portable across machines; consumers resolve them against the directory holding `.tactica`. Earlier versions emitted absolute paths, so consumers should accept both.
 
 | File | When | Purpose |
 |---|---|---|
@@ -359,7 +361,7 @@ Tactica then emits:
 - Prefixed instance types in `.tactica/types.ts`, e.g. `AppCollectionRegistry_UserType` and `AppCollectionRegistry_UserType_AdminType`.
 - A `declare module '<relative path to this file>'` block in `.tactica/registry.ts` that augments `AppCollectionRegistry` with `'UserType'` and `'UserType.AdminType'` entries.
 
-Once `.tactica/registry.ts` is part of your `tsc` compilation, `AppCollection.lookup('UserType')` and `AppCollection.lookup('UserType.AdminType')` are fully typed.
+Once `.tactica/registry.ts` is part of your `tsc` compilation, `AppCollection.lookup('UserType')` and `AppCollection.lookup('UserType.AdminType')` are fully typed. Constructor-relative lookups resolve too: a variable bound to `AppCollection.lookup('UserType')` resolves `.lookup('AdminType')` relative-first (the type's own subtypes, then the collection root) — the same law as for default-collection types.
 
 Custom collections also support `decorate()` for root types:
 
@@ -473,7 +475,7 @@ The analyzer infers property types from constructor bodies and class members. Su
 | `this.x = []` / `new Array()` | `Array<…>` |
 | `this.x = {}` | `object` |
 | `this.x = new Date()` | `Date` |
-| `this.x = new Map()` / `new Set()` | `Map<…>` / `Set<…>` |
+| `this.x = new Map()` / `new Set()` | `Map<unknown, unknown>` / `Set<unknown>` — a bare generic is never emitted (TS2314); explicit arguments survive: `new Map<string, number>()` → `Map<string, number>` |
 | `this.x = Date.now()` | `number` |
 | `this.x = parseInt(…)` / `parseFloat(…)` | `number` |
 | `this.x = String(…)` / `Number(…)` / `Boolean(…)` | `string` / `number` / `boolean` |
@@ -705,7 +707,7 @@ class ModuleGraphBuilder {
 
 `ModuleGraph` = `{ modules: Map<absPath, ModuleInfo>, edges: CrossModuleUsage[], cycles: string[][] }`.
 Each `ModuleBinding` carries `{ name, kind: 'function'|'class'|'const'|'type'|'unknown',
-sourceModule (resolved absolute path), importKind?, importAlias?, isReExport, external? }`.
+sourceModule (resolved project-relative path), importKind?, importAlias?, isReExport, external? }`.
 Node.js builtins (`'path'`, `'node:fs'`, …) are skipped entirely and recorded
 only in the module's `builtinSpecifiers`; bindings resolved into `node_modules`
 carry `external: true` and never enter `dependencies`. Re-export chains
@@ -789,7 +791,7 @@ When enabled, tactica detects execution-flow patterns alongside type definitions
     "eds": {
         "UserEntity": [
             {
-                "location": "/project/src/queue.ts:45:12",
+                "location": "src/queue.ts:45:12",
                 "kind": "wrap",
                 "code": "wrap(process)",
                 "targetType": "UserEntity"
@@ -859,7 +861,7 @@ When a referenced class is declared in the analyzed project, the point's `locati
         {
             "kind": "pipe",
             "className": "PayloadPipe",
-            "location": "/project/src/user.controller.ts:49:2",
+            "location": "src/user.controller.ts:49:2",
             "code": "@RegisterPipe(new PayloadPipe({ transform: true }))",
             "scope": "method:UserController.createUser",
             "targets": ["UserController"]
@@ -868,21 +870,21 @@ When a referenced class is declared in the analyzed project, the point's `locati
     "creationGraph": {
         "nodes": [
             {
-                "scopeId": "/project/src/main.ts",
-                "name": "/project/src/main.ts",
+                "scopeId": "src/main.ts",
+                "name": "src/main.ts",
                 "kind": "module",
-                "filePath": "/project/src/main.ts",
-                "location": "/project/src/main.ts:1:1",
+                "filePath": "src/main.ts",
+                "location": "src/main.ts:1:1",
                 "starter": true
             }
         ],
         "edges": [
-            { "caller": "/project/src/main.ts", "callee": "/project/src/user.service.ts:26:2" }
+            { "caller": "src/main.ts", "callee": "src/user.service.ts:26:2" }
         ],
         "anchors": [
             {
-                "location": "/project/src/user.service.ts:29:24",
-                "holderScopeId": "/project/src/user.service.ts:26:2",
+                "location": "src/user.service.ts:29:24",
+                "holderScopeId": "src/user.service.ts:26:2",
                 "typePath": "UserEntity.UserResponse",
                 "constructorText": "user.UserResponse",
                 "variable": "userResponse"