@noctcore/lint-meta-rules 0.5.0 → 0.6.1

package/docs/rules/translation-dead-keys.md

@@ -3,6 +3,10 @@
 > Every translation catalog key is reachable from the source: named by a translation call, or spelled
 > by some string in the code.
 
+<!-- begin generated rule header -->
+Runs under `@noctcore/harness`, not ESLint · Factory `createTranslationDeadKeysRule` from `@noctcore/lint-meta-rules/i18n` · Category `source-text` · Fails CI by default: yes
+<!-- end generated rule header -->
+
 Import it from the `i18n` entry point, which (unlike the main one) loads ESLint:
 
 ```ts
@@ -21,7 +25,27 @@ This rule resolves call sites with the same visitor and catalog loader as
 two checks never disagree on which key a call means. It then adds the data routes a per-file rule
 cannot see.
 
-## What counts as reached
+## What it flags
+
+Every key in `catalogs` that no scanned source reaches (the routes are listed under
+[What it does not flag](#what-it-does-not-flag)). What is left was named by no call and spelled by no
+string. On a production app with 1,824 keys this reported 55, and every one of them had zero
+references outside the catalogs.
+
+### Blind spots
+
+It is conservative, not complete. It reports a reached key as dead when the key arrives by a route it
+cannot see:
+
+- **Keys that never appear in the scanned source**: server-sent codes, a CMS, another app, JSON
+  config. List them in `allow`, or add the files that spell them to `sourceGlobs`.
+- **A variable key under a `keyPrefix` binding**: `useTranslation('ns', { keyPrefix: 'form' })` then
+  `t(field)` with `field = 'name'` reaches `form.name`, but no string spells `form.name`. (A static key
+  under a `keyPrefix` is resolved correctly.)
+- **Keys built by anything other than `+` or a template literal**: `[a, b].join('.')`,
+  `` `${a}` `` split across variables, `String.prototype.concat`.
+
+## What it does not flag
 
 A key is reached, and never reported, when ANY of these holds:
 
@@ -36,29 +60,13 @@ A key is reached, and never reported, when ANY of these holds:
   `` `nav.${id}.label` `` and `'errors.' + code` are patterns, not just call arguments;
 - it matches an `allow` pattern.
 
-And it reports **no dead key at all** when a scanned file cannot be analysed (a parse error), or when
+It reports **no dead key at all** when a scanned file cannot be analysed (a parse error), or when
 `sourceGlobs` match nothing: in both cases the rule would otherwise call reached keys dead.
 
-What is left was named by no call and spelled by no string. On a production app with 1,824 keys this
-reported 55, and every one of them had zero references outside the catalogs.
-
-## Blind spots
-
-It is conservative, not complete. It reports a reached key as dead when the key arrives by a route it
-cannot see:
-
-- **Keys that never appear in the scanned source**: server-sent codes, a CMS, another app, JSON
-  config. List them in `allow`, or add the files that spell them to `sourceGlobs`.
-- **A variable key under a `keyPrefix` binding**: `useTranslation('ns', { keyPrefix: 'form' })` then
-  `t(field)` with `field = 'name'` reaches `form.name`, but no string spells `form.name`. (A static key
-  under a `keyPrefix` is resolved correctly.)
-- **Keys built by anything other than `+` or a template literal**: `[a, b].join('.')`,
-  `` `${a}` `` split across variables, `String.prototype.concat`.
-
 It also misses some dead keys, by design: any string that happens to equal a key (in any namespace)
 keeps it alive, and a broad pattern such as `` `${x}.title` `` keeps every `*.title` alive.
 
-## Factory
+## Options
 
 ```ts
 createTranslationDeadKeysRule(options?: TranslationDeadKeysOptions): IMetaRule
@@ -92,7 +100,12 @@ createTranslationDeadKeysRule({
 });
 ```
 
-## Requirements
+### Requirements
 
 The `i18n` entry needs the optional peers `eslint` (>= 9) and `@typescript-eslint/parser`. Scanned
 files are parsed as TypeScript with JSX enabled, without type information.
+
+## When not to use it
+
+If most keys reach the app from outside the scanned source (server-sent codes, a CMS, another app),
+`allow` would have to list most of the catalog and the rule proves little, so skip it.

package/docs/rules/ui-primitive-shape.md

@@ -2,6 +2,10 @@
 
 > A folder primitive must ship its proof siblings; a flat primitive must carry none at the ui root.
 
+<!-- begin generated rule header -->
+Runs under `@noctcore/harness`, not ESLint · Factory `createUiPrimitiveShapeRule` from `@noctcore/lint-meta-rules` · Category `source-text` · Fails CI by default: yes
+<!-- end generated rule header -->
+
 ## Why
 
 The primitives root is the one place exempt from folder-per-component: flat single files are fine for
@@ -18,7 +22,15 @@ tested + storied.
   `<Name>.<role><extension>` at the ui root is flagged: those proof files belong inside a `<Name>/`
   folder.
 
-## Factory
+## What it does not flag
+
+- A bare flat primitive (`<uiRoot>/Button.tsx`) with no proof sibling at the ui root.
+- A folder primitive that ships every configured role (`Dialog/Dialog.test.tsx`,
+  `Dialog/Dialog.stories.tsx`).
+- A folder without the `barrelFile`, and flat files whose name does not start with a capital letter.
+- Anything outside `uiRoot`.
+
+## Options
 
 ```ts
 createUiPrimitiveShapeRule(options?: UiPrimitiveShapeOptions): IMetaRule
@@ -32,9 +44,6 @@ createUiPrimitiveShapeRule(options?: UiPrimitiveShapeOptions): IMetaRule
 | `extension` | `string` | `'.tsx'` | Extension of primitive and proof files. |
 | `ciCritical` | `boolean` | `true` | Whether a violation fails CI. |
 
-De-projected from nightcore, which hardcoded `apps/web/src/components/ui`, the `test`/`stories` roles,
-and the `.tsx` extension.
-
 ## When not to use it
 
 If you do not maintain a flat-vs-folder primitive convention or do not colocate stories/tests, skip

package/docs/rules/workspace-graph-parity.md

@@ -3,6 +3,10 @@
 > Imported `<scope>/*` specifiers must be declared `workspace:*` deps, and tsconfig `references` must
 > mirror those deps.
 
+<!-- begin generated rule header -->
+Runs under `@noctcore/harness`, not ESLint · Factory `createWorkspaceGraphParityRule` from `@noctcore/lint-meta-rules` · Category `config` · Fails CI by default: yes
+<!-- end generated rule header -->
+
 ## Why
 
 A cross-package edge is real in three places at once: the import in source, the `workspace:*` entry in
@@ -14,13 +18,21 @@ so an edge can never be half-wired.
 
 For each workspace `package.json`:
 
-- **(a) imported ⊆ declared** — every `<scope>/<pkg>` imported under the source dir (test files
-  excluded, self-imports ignored) must appear as a `"<scope>/<pkg>": "workspace:*"` dependency.
+- **(a) imported ⊆ declared** — every `<scope>/<pkg>` imported under the source dir must appear as a
+  `"<scope>/<pkg>": "workspace:*"` dependency.
 - **(b) references mirror deps** — the tsconfig `references` must reference exactly the declared
   workspace deps: a declared dep missing from references, or a referenced package that is not a
   declared dep, is a violation.
 
-## Factory
+## What it does not flag
+
+- A package importing itself by its own `<scope>/<dir>` name.
+- Imports in test files (`.test.ts`, `.test.tsx`) and files outside `srcDir`.
+- Imports without a `from` clause (`import()`, `require()`, a side-effect `import`): only
+  `from '<scope>/<pkg>'` is read.
+- Check (b) for a package with no `tsconfig.json`.
+
+## Options
 
 ```ts
 createWorkspaceGraphParityRule(options?: WorkspaceGraphParityOptions): IMetaRule
@@ -33,8 +45,6 @@ createWorkspaceGraphParityRule(options?: WorkspaceGraphParityOptions): IMetaRule
 | `srcDir` | `string` | `'src'` | Source directory (per package) scanned for imports. |
 | `ciCritical` | `boolean` | `true` | Whether a violation fails CI. |
 
-De-projected from nightcore, which hardcoded the `@nightcore` scope and a `src` source directory.
-
 ## When not to use it
 
 If your project does not use the `workspace:*` protocol, or does not use TypeScript project

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@noctcore/lint-meta-rules",
-  "version": "0.5.0",
+  "version": "0.6.1",
   "description": "Portable, parameterized lint-meta rules — whole-repo / cross-file invariants ESLint cannot reach — for the @noctcore/harness lint-meta runner.",
   "license": "MIT",
   "type": "module",
@@ -28,6 +28,16 @@
       "import": "./dist/resolved-config.js",
       "require": "./dist/resolved-config.cjs"
     },
+    "./session": {
+      "types": "./dist/session.d.ts",
+      "import": "./dist/session.js",
+      "require": "./dist/session.cjs"
+    },
+    "./trpc": {
+      "types": "./dist/trpc.d.ts",
+      "import": "./dist/trpc.js",
+      "require": "./dist/trpc.cjs"
+    },
     "./package.json": "./package.json"
   },
   "files": [
@@ -53,16 +63,16 @@
     "url": "git+https://github.com/noctcore/eslint-plugins.git",
     "directory": "packages/lint-meta-rules"
   },
-  "homepage": "https://github.com/noctcore/eslint-plugins/tree/main/packages/lint-meta-rules",
+  "homepage": "https://noctcore.github.io/eslint-plugins/packages/lint-meta-rules/",
   "bugs": "https://github.com/noctcore/eslint-plugins/issues",
   "scripts": {
-    "build": "tsup src/index.ts src/i18n.ts src/prisma.ts src/resolved-config.ts --format esm,cjs --dts --clean",
+    "build": "tsup src/index.ts src/i18n.ts src/prisma.ts src/resolved-config.ts src/session.ts src/trpc.ts --format esm,cjs --dts --clean",
     "typecheck": "tsc --noEmit",
     "test": "bun test"
   },
   "dependencies": {
-    "@noctcore/eslint-plugin-contracts": "^0.7.0",
-    "@noctcore/eslint-plugin-prisma": "^0.5.0",
+    "@noctcore/eslint-plugin-contracts": "^0.7.1",
+    "@noctcore/eslint-plugin-prisma": "^0.5.1",
     "@noctcore/harness": "^0.3.0",
     "@typescript-eslint/utils": "^8.61.1"
   },
@@ -79,9 +89,9 @@
     }
   },
   "devDependencies": {
-    "@types/node": "^22.0.0",
-    "@typescript-eslint/parser": "^8.61.1",
-    "eslint": "^10.7.0",
+    "@types/node": "^22.20.3",
+    "@typescript-eslint/parser": "^8.70.0",
+    "eslint": "^10.10.0",
     "tsup": "^8.5.1",
     "typescript": "^5.6.0"
   }