eslint-plugin-llm-core-mcp 0.27.1 โ 0.27.3
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"embedded-docs.d.ts","sourceRoot":"","sources":["../src/embedded-docs.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,YAAY,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,
|
|
1
|
+
{"version":3,"file":"embedded-docs.d.ts","sourceRoot":"","sources":["../src/embedded-docs.ts"],"names":[],"mappings":"AAEA,eAAO,MAAM,YAAY,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAoC/C,CAAC;AAEF,eAAO,MAAM,SAAS,EAAE,MAAM,EAA6yB,CAAC"}
|
package/dist/embedded-docs.js
CHANGED
|
@@ -20,6 +20,7 @@ export const embeddedDocs = {
|
|
|
20
20
|
"no-exported-function-expressions": "# llm-core/no-exported-function-expressions\n\n๐ Enforce that exported functions use function declarations instead of function expressions or arrow functions.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, โ
`recommended`, ๐จ `style`.\n\n๐ก This rule is manually fixable by [editor suggestions](https://eslint.org/docs/latest/use/core-concepts#rule-suggestions).\n\n<!-- end auto-generated rule header -->\n\nEnforce that exported functions use function declarations instead of function expressions or arrow functions.\n\n## Rationale\n\nLLMs consistently default to `export const fn = () => {}` when generating code. Function declarations are preferred because:\n\n- **Hoisting**: Function declarations are hoisted, making code order more flexible\n- **Stack traces**: Named function declarations produce clearer stack traces for debugging\n- **Intent**: Declarations signal \"this is a named function\" more clearly than variable assignments\n- **Consistency**: Enforces a single style across the codebase\n\nThis rule provides structured error messages that teach the LLM the correct pattern. Through iteration, the LLM learns to use function declarations automatically.\n\n## Rule Details\n\nThis rule reports when:\n\n1. A named export uses an arrow function or function expression (`export const fn = () => {}`)\n2. A default export uses an anonymous arrow function (`export default () => {}`)\n3. A default export uses an anonymous function expression (`export default function() {}`)\n\n### What This Rule Catches\n\n| Pattern | Caught? |\n| ---------------------------------------- | ---------- |\n| `export const fn = () => {}` | Yes |\n| `export const fn = async () => {}` | Yes |\n| `export const fn = function() {}` | Yes |\n| `export const fn = async function() {}` | Yes |\n| `export default () => {}` | Yes |\n| `export default function() {}` | Yes |\n| `export function fn() {}` | No (valid) |\n| `export default function fn() {}` | No (valid) |\n| `const fn = () => {}` (non-exported) | No (valid) |\n| `export const value = 42` (non-function) | No (valid) |\n\n## Examples\n\n### Incorrect\n\n```ts\n// Arrow function exports\nexport const fetchData = async () => {\n return await api.get('/data');\n};\n\n// Function expression exports\nexport const processItem = function(item) {\n return item.value * 2;\n};\n\n// Anonymous default exports\nexport default () => <div>Hello</div>;\n\n// Expression body arrows\nexport const double = (x: number) => x * 2;\n```\n\n### Correct\n\n```ts\n// Named function declarations\nexport async function fetchData() {\n return await api.get('/data');\n}\n\nexport function processItem(item) {\n return item.value * 2;\n}\n\n// Named default export\nexport default function HelloComponent() {\n return <div>Hello</div>;\n}\n\nexport function double(x: number) {\n return x * 2;\n}\n\n// Non-exported arrow functions are fine (internal helpers)\nconst helper = () => 'internal';\n```\n\n## Suggestions\n\nThis rule provides manual fix suggestions (not auto-fix) to convert function expressions to declarations. Auto-fix is intentionally avoided because converting arrow functions to declarations can change `this` binding semantics in some contexts.\n\n## No Escape Hatches\n\nFollowing the [deterministic linting approach](https://understandingdata.com/posts/custom-eslint-rules-determinism/), this rule is designed to be used alongside `eslint-comments/no-use` or similar rules that prevent `eslint-disable` comments. This ensures LLM agents cannot bypass the rule and must learn the correct pattern.\n\n## Error Message Format\n\nError messages follow a structured teaching format:\n\n1. **What's wrong**: Clear statement of the violation\n2. **Why**: Explanation of why the pattern is preferred\n3. **How to fix**: Concrete before/after code example\n\nThis format is designed to be parseable by LLMs, enabling self-correction through the lint-fix loop.\n",
|
|
21
21
|
"no-floating-promise": "# llm-core/no-floating-promise\n\n๐ Disallow calling async functions or Promise-returning expressions without awaiting, returning, or explicitly voiding the result.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, ๐ `best-practices`, โ
`recommended`.\n\n<!-- end auto-generated rule header -->\n\n## Rule Details\n\nLLMs frequently call async functions and drop the returned Promise. A floating Promise loses its rejection (turning into an unhandled promise rejection), breaks execution ordering, and is one of the most common async bugs in generated code.\n\nThis rule flags three AST-detectable patterns at statement position, without requiring TypeScript type information:\n\n1. **Async function references** โ a call whose callee resolves, in the current file, to an `async function` declaration or a variable initialized to an async arrow/function expression.\n2. **Promise factory calls** โ `Promise.all`, `Promise.allSettled`, `Promise.race`, `Promise.any`, `Promise.resolve`, and `Promise.reject`.\n3. **Unhandled `.then()` chains** โ a top-level `.then(handler)` call with fewer than two arguments (so the rejection path has no handler).\n\nThe rule fires only when the call is the expression of an `ExpressionStatement`. Calls consumed by `await`, `return`, `void`, a variable declarator, or an assignment are not statements and are never flagged.\n\n## When Not To Use It\n\nThis rule uses AST heuristics, not TypeScript's type checker. If your project enables `@typescript-eslint/no-floating-promises` with full type information, prefer that rule โ it catches strictly more floating Promises. Use this rule when a type-aware lint is not available, or as an additional teaching-message layer on top.\n\n## Examples\n\n### Incorrect\n\n```ts\nasync function saveData() {\n /* ... */\n}\n\n// Async function call at statement position โ result is discarded\nsaveData();\n\n// Promise factory at statement position\nPromise.all([p1, p2]);\n\n// .then() chain without a rejection handler\nfetchData().then((data) => process(data));\n```\n\n### Correct\n\n```ts\nasync function saveData() {\n /* ... */\n}\n\n// Await the result\nawait saveData();\n\n// Return it to the caller\nasync function run() {\n return saveData();\n}\n\n// Store for later awaiting\nasync function run() {\n const p = saveData();\n await p;\n}\n\n// Explicit fire-and-forget\nvoid saveData();\n\n// Attach a rejection handler\nsaveData().catch((error) => logger.error(\"save failed\", error));\n\n// Two-argument .then() handles both paths\nfetchData().then(handle, onError);\n\n// Chain ends with .catch()\nfetchData()\n .then(handle)\n .catch((error) => logger.error(error));\n```\n\n## Detected Patterns\n\n| Pattern at statement position | Flagged? |\n| ---------------------------------------- | -------- |\n| `asyncFn();` (declared async in scope) | Yes |\n| `Promise.all([p1, p2]);` | Yes |\n| `Promise.resolve(x);` | Yes |\n| `foo().then(handler);` | Yes |\n| `foo().then(handler, onError);` | No |\n| `foo().catch(handler);` | No |\n| `foo().then(handler).catch(onError);` | No |\n| `void asyncFn();` | No |\n| `await asyncFn();` / `return asyncFn();` | No |\n\n## Error Messages\n\nThe error message teaches:\n\n1. **What's wrong** โ the returned Promise at statement position is discarded\n2. **Why** โ dropped Promises lose their rejection and break execution ordering\n3. **How to fix** โ `await`, `return`, `void`, or attach `.catch(...)`\n",
|
|
22
22
|
"no-hallucinated-local-imports": "# llm-core/no-hallucinated-local-imports\n\n๐ Disallow static relative imports and re-exports that reference missing local modules or named exports.\n\n๐ผ This rule is enabled in the ๐ `all` config.\n\n<!-- end auto-generated rule header -->\n\nDisallow static relative `import` and `export ... from` declarations that point to missing local modules or request named exports that the target module does not directly export.\n\n## Rule Details\n\nLLM coding agents often invent nearby file names or helper export names that sound plausible in the current codebase. These hallucinated imports are high-signal failures: the code usually cannot build, type-check, or run.\n\nThis rule is intentionally narrow for v1:\n\n- checks only relative local paths that start with `./` or `../`\n- checks only static `import` declarations and `export ... from` re-exports\n- resolves explicit files, common JS/TS extensions, and `index` files\n- checks direct named exports in the resolved module\n- ignores package imports, path aliases, dynamic imports, and re-export chains\n\n## Examples\n\n### Incorrect\n\n```ts\nimport { createCache } from \"./cache-utils\";\n// ./cache-utils does not resolve to a local file\n\nimport { createCacheFactory } from \"./cache\";\n// ./cache exists, but it does not directly export createCacheFactory\n\nexport { parseUser } from \"../users/parser\";\n// ../users/parser exists, but parseUser is not directly exported there\n```\n\n### Correct\n\n```ts\nimport { createCache } from \"./cache\";\nimport { parseUserRecord } from \"../users/parser\";\nexport { createCache } from \"./cache\";\n```\n\n## What This Rule Flags\n\n| Import/export shape | Flagged? |\n| ------------------------------------------ | -------- |\n| `import { x } from \"./missing\"` | โ
Yes |\n| `export { x } from \"./missing\"` | โ
Yes |\n| `import { missing } from \"./existing\"` | โ
Yes |\n| `import { existing } from \"./existing\"` | โ No |\n| `import pkg from \"package\"` | โ No |\n| `import(\"./missing\")` | โ No |\n| `import { x } from \"@/aliased/module\"` | โ No |\n| indirect export through a barrel/re-export | โ No |\n\n## Error Messages\n\nThe teaching messages explain:\n\n1. **What's wrong** โ the local module path or named export does not exist\n2. **Why** โ hallucinated imports are a common LLM failure mode that break builds\n3. **How to fix** โ update the import to an existing local module/export, or add the missing export intentionally\n",
|
|
23
|
+
"no-hallucinated-package-imports": "# llm-core/no-hallucinated-package-imports\n\n๐ Disallow package imports and re-exports whose package root is not declared in the relevant package manifest.\n\n๐ผ This rule is enabled in the ๐ `all` config.\n\n<!-- end auto-generated rule header -->\n\nDisallow package `import` and `export ... from` declarations when the package root is not declared in the relevant package manifest.\n\n## Rule Details\n\nLLM coding agents often invent plausible package names, assume a dependency is already installed, or import from a package that exists in another project but not in the current one. These hallucinated package imports look reasonable during review but fail at install, build, test, or runtime.\n\nThis rule reports package roots that are absent from the configured package manifest dependency sources. It intentionally ignores relative and absolute local paths because `llm-core/no-hallucinated-local-imports` handles local modules.\n\nBy default, this rule treats these sources as allowed:\n\n- `dependencies`\n- `devDependencies`\n- `peerDependencies`\n- `optionalDependencies`\n- Node.js builtins, including `node:` specifiers\n- the current package's own `name` for valid package self-references\n- workspace package names discovered from explicit workspace paths and simple workspace glob patterns such as `packages/*`\n- packages listed in the `allow` option\n\n## Examples\n\n### Incorrect\n\n```ts\nimport { retry } from \"super-retry-utils\";\n// super-retry-utils is not declared in package.json\n\nimport type { Client } from \"@vendor/nonexistent-sdk\";\n// @vendor/nonexistent-sdk is not declared in package.json\n\nexport { thing } from \"plausible-helper-package\";\n// plausible-helper-package is not declared in package.json\n\nconst mod = await import(\"made-up-package\");\n// made-up-package is not declared in package.json\n```\n\n### Correct\n\n```ts\nimport { readFile } from \"node:fs/promises\";\nimport path from \"node:path\";\nimport { z } from \"zod\";\n// zod is declared in package.json\n\nimport { helper } from \"./helper\";\n// relative imports are handled by no-hallucinated-local-imports\n\nimport internal from \"@workspace/internal-package\";\n// workspace package names are allowed when workspace discovery is enabled\n\nimport selfConfig from \"my-package/config\";\n// package self-references are allowed when package.json has \"name\": \"my-package\"\n\nimport localAlias from \"@/utils\";\n// common @/ path aliases are ignored because they are not valid npm package roots\n```\n\n## Options\n\n```ts\ntype Options = [\n {\n packageJsonPath?: string;\n workspace?: boolean;\n allow?: string[];\n checkDevDependencies?: boolean;\n checkPeerDependencies?: boolean;\n checkOptionalDependencies?: boolean;\n checkDynamicImports?: boolean;\n checkRequire?: boolean;\n },\n];\n```\n\n| Option | Default | Description |\n| --------------------------- | ------- | ----------------------------------------------------------------------------- |\n| `packageJsonPath` | nearest | Package manifest to inspect. If omitted, the nearest `package.json` is used. |\n| `workspace` | `true` | Allow workspace package names from explicit paths and simple workspace globs. |\n| `allow` | `[]` | Additional exact specifiers or package roots to allow. |\n| `checkDevDependencies` | `true` | Treat `devDependencies` as allowed. Set to `false` to report them. |\n| `checkPeerDependencies` | `true` | Treat `peerDependencies` as allowed. Set to `false` to report them. |\n| `checkOptionalDependencies` | `true` | Treat `optionalDependencies` as allowed. Set to `false` to report them. |\n| `checkDynamicImports` | `true` | Check dynamic `import(\"literal\")` package specifiers. |\n| `checkRequire` | `false` | Check CommonJS `require(\"literal\")` package specifiers. |\n\n## What This Rule Flags\n\n| Import/export shape | Flagged? |\n| ---------------------------------------------- | -------- |\n| `import { x } from \"missing-package\"` | โ
Yes |\n| `import type { X } from \"@scope/missing\"` | โ
Yes |\n| `export * from \"missing-package/subpath\"` | โ
Yes |\n| `import { x } from \"declared-package/subpath\"` | โ No |\n| `import { readFile } from \"node:fs/promises\"` | โ No |\n| `import { helper } from \"./helper\"` | โ No |\n| `await import(variableName)` | โ No |\n| `require(\"missing-package\")` by default | โ No |\n\n## Error Messages\n\nThe teaching message explains:\n\n1. **What's wrong** โ the imported package root is not declared in the relevant package manifest\n2. **Why** โ hallucinated package imports hide dependency changes and break install/build/test/runtime paths\n3. **How to fix** โ use an existing declared dependency, add the dependency intentionally, or configure an explicit allow/workspace entry\n",
|
|
23
24
|
"no-incorrect-sort": "# llm-core/no-incorrect-sort\n\n๐ Disallow .sort() without a compare function, which coerces elements to strings and produces incorrect numeric ordering.\n\n๐ผ This rule is enabled in the ๐ `all` config.\n\n<!-- end auto-generated rule header -->\n\n## Rule details\n\nThis rule flags `.sort()` calls that omit a compare function. JavaScript's default sort converts elements to strings before comparing, so `[10, 2, 1].sort()` produces `[1, 10, 2]` instead of `[1, 2, 10]`.\n\nFlagged patterns:\n\n```js\nnums.sort(); // no compare function\narr.sort(undefined); // undefined is not a comparator\narr.sort(void 0); // void 0 is semantically undefined\n```\n\nCorrect patterns:\n\n```js\nnums.sort((a, b) => a - b); // numeric ascending\nnames.sort((a, b) => a.localeCompare(b)); // locale-aware string\nitems.sort((a, b) => a.name.localeCompare(b.name)); // object property\n```\n\n## Scope and limitations\n\nThis rule operates on static AST analysis without type information. It:\n\n- **Skips TypedArray receivers** โ `new Int32Array([...]).sort()` is correct because `%TypedArray%.prototype.sort` uses numeric comparison by default.\n- **Does not track variable types** โ `const buffer = new Float64Array(data); buffer.sort();` will be flagged because the receiver is a plain identifier, not a `new` expression. For files with known TypedArray variables, disable the rule at the config level:\n ```js\n // eslint.config.mjs\n export default [\n { ignores: [\"src/buffers/*.ts\"] },\n // or: { files: [\"src/buffers/*.ts\"], rules: { \"llm-core/no-incorrect-sort\": \"off\" } },\n ];\n ```\n- **May flag custom APIs** โ Methods named `.sort()` on query builders, ORM cursors, or RxJS observables have no relation to `Array.prototype.sort`. Disable the rule in those scopes.\n",
|
|
24
25
|
"no-inline-disable": "# llm-core/no-inline-disable\n\n๐ Disallow eslint-disable comments that suppress lint errors instead of fixing them.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, ๐งน `hygiene`, โ
`recommended`.\n\n<!-- end auto-generated rule header -->\n\nDisallow eslint-disable comments that suppress lint errors instead of fixing them.\n\n## Rule Details\n\nLLMs frequently add `// eslint-disable-next-line` or `/* eslint-disable */` comments to silence lint errors rather than fixing the underlying code. This bypasses all other lint rules, defeating the purpose of linting.\n\nThis rule catches:\n\n- `// eslint-disable-next-line`\n- `// eslint-disable-line`\n- `/* eslint-disable ... */`\n- `/* eslint-enable ... */`\n\n## Examples\n\n### Incorrect\n\n```ts\n// eslint-disable-next-line no-unused-vars\nconst x = 1;\n\n/* eslint-disable no-console */\nconsole.log(\"debug\");\n/* eslint-enable no-console */\n\nconst y = 1; // eslint-disable-line no-unused-vars\n```\n\n### Correct\n\n```ts\n// Fix the code instead of disabling the rule\nconst x = computeValue();\nuseValue(x);\n\n// Use a proper logger instead of console\nlogger.debug(\"debug info\", { context });\n\n// If a rule doesn't apply to certain files, configure it in eslint.config.mjs\n// instead of disabling inline\n```\n\n## Why No Escape Hatches?\n\nWhen an LLM encounters a lint error, it has two options:\n\n1. Fix the code to satisfy the rule\n2. Add a disable comment to suppress the error\n\nOption 2 is always easier, so LLMs default to it. This rule removes that escape hatch, forcing the LLM to actually fix the code โ which is the entire point of linting.\n\n## Error Messages\n\nError messages follow a structured teaching format designed for LLM self-correction:\n\n1. **What's wrong** โ identifies the specific disable comment\n2. **Why** โ explains that suppressing rules hides problems\n3. **How to fix** โ three alternatives: fix the code, configure the rule properly, or refactor\n",
|
|
25
26
|
"no-llm-artifacts": "# llm-core/no-llm-artifacts\n\n๐ Disallow common LLM placeholder comments and incomplete code markers that indicate skipped implementation.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, ๐งน `hygiene`, โ
`recommended`.\n\n<!-- end auto-generated rule header -->\n\nDisallow common LLM placeholder comments and stub function bodies that indicate incomplete code generation.\n\n## Rule Details\n\nLLMs frequently save tokens by outputting placeholder comments like `// ... existing code ...`, `// TODO: implement`, or `// rest of the function remains the same` instead of writing the actual code. When applied automatically by an agent, these placeholders silently replace real logic with nothing.\n\nThis rule detects two categories of LLM artifacts:\n\n1. **Placeholder comments** โ Comments that indicate skipped or abbreviated code\n2. **Stub function bodies** โ Functions whose only statement is `throw new Error(\"Not implemented\")`\n\n## Examples\n\n### Incorrect\n\n```ts\n/* eslint llm-core/no-llm-artifacts: \"error\" */\n\n// ... existing code ...\nfunction processData(items: Item[]) {\n // implementation goes here\n}\n\n// rest of the function remains the same\n\nfunction validate(input: string) {\n throw new Error(\"Not implemented\");\n}\n\n// abbreviated for brevity\n// add error handling as needed\n```\n\n### Correct\n\n```ts\n/* eslint llm-core/no-llm-artifacts: \"error\" */\n\n// This function processes items by filtering and transforming\nfunction processData(items: Item[]) {\n return items.filter(isValid).map(transform);\n}\n\n// TODO(#123): add caching for repeated lookups\nfunction validate(input: string) {\n if (!input.trim()) {\n throw new Error(\"Input must not be empty\");\n }\n return schema.parse(input);\n}\n```\n\n## Detected Patterns\n\n### Placeholder Comments\n\n| Pattern | Example |\n| ---------------------- | ---------------------------------------------------------- |\n| Ellipsis placeholders | `// ... existing code ...`, `// ...rest of the code...` |\n| \"Remains the same\" | `// rest of the function remains the same` |\n| Lazy TODO | `// TODO: implement`, `// TODO implement` |\n| \"Code here\" markers | `// add implementation here`, `// your code here` |\n| \"As needed\" deferrals | `// add error handling as needed` |\n| Brevity markers | `// abbreviated for brevity`, `// omitted for clarity` |\n| Reference to elsewhere | `// similar to above`, `// same as before` |\n| \"Continue here\" | `// continue from here`, `// continue implementation here` |\n| \"See above/below\" | `// see implementation above`, `// see above for details` |\n\n### Stub Function Bodies\n\nFunctions whose only statement is `throw new Error(msg)` where `msg` matches \"not implemented\" or \"TODO: implement\" (case-insensitive).\n\n## What This Rule Allows\n\n- **Specific TODOs** โ `// TODO(#123): validate input against schema` (has actionable context)\n- **Prose comments** โ `// This handles the edge case where input is empty`\n- **Legitimate throws** โ `throw new Error(\"XML format is not supported\")` (real error, not a placeholder)\n- **Functions with real logic** โ Even if they contain a \"not implemented\" throw alongside other statements\n\n## Error Messages\n\n### `noLlmArtifact`\n\n> LLM placeholder detected: '...'. Replace with actual implementation.\n\nFired for placeholder comments. The message explains that these comments replace real logic when applied, and suggests writing specific TODOs if work must be deferred.\n\n### `notImplementedStub`\n\n> Function body is a 'not implemented' stub โ write the actual implementation.\n\nFired for functions whose sole body is a \"not implemented\" throw. The message explains that these stubs pass type checks but fail at runtime.\n",
|
|
@@ -27,6 +28,7 @@ export const embeddedDocs = {
|
|
|
27
28
|
"no-redundant-logic": "# llm-core/no-redundant-logic\n\n๐ Disallow redundant boolean logic and unnecessary control flow patterns.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, โ
`recommended`, ๐จ `style`.\n\n๐ก This rule is manually fixable by [editor suggestions](https://eslint.org/docs/latest/use/core-concepts#rule-suggestions).\n\n<!-- end auto-generated rule header -->\n\nFlags four patterns where LLMs produce verbose-but-correct boolean logic that can be simplified without changing semantics.\n\n## Rule Details\n\n### Pattern 1 โ Redundant boolean comparison\n\nExplicit `=== true`, `!== true`, `=== false`, or `!== false` comparisons on an expression that already evaluates to a boolean.\n\nOnly strict equality (`===`/`!==`) is flagged. Loose equality (`==`/`!=`) has different truthy/falsy semantics and is intentionally excluded.\n\n> **Known limitation:** This rule does not use type information. If the compared expression is a union type (e.g., `string | boolean`), the `=== true` comparison may be intentional type narrowing, not a redundant check. Disable the rule on that line if this applies.\n\n#### Incorrect\n\n```ts\nif (isActive === true) {\n}\nif (isValid !== true) {\n}\nif (hasPermission === false) {\n}\nwhile (running !== false) {}\n```\n\n#### Correct\n\n```ts\nif (isActive) {\n}\nif (!isValid) {\n}\nif (!hasPermission) {\n}\nwhile (running) {}\n```\n\n### Pattern 2 โ Unnecessary else after return/throw\n\nAn `else` block that follows an `if` block ending in `return` or `throw` is unreachable via fall-through. The `else` can be removed and its body placed at the outer scope.\n\nOnly flags when:\n\n- The `if` consequent ends with `return` or `throw`\n- The `else` is a simple block (single `return` or `throw`), not an `else if` chain\n- Pattern 4 does not apply to the same node (to avoid double-reporting)\n\n#### Incorrect\n\n```ts\nfunction getLabel(status: string): string {\n if (status === \"active\") {\n return \"Active\";\n } else {\n return \"Inactive\";\n }\n}\n```\n\n#### Correct\n\n```ts\nfunction getLabel(status: string): string {\n if (status === \"active\") {\n return \"Active\";\n }\n return \"Inactive\";\n}\n```\n\n### Pattern 3 โ Ternary returning boolean literals\n\nA ternary of the form `condition ? true : false` or `condition ? false : true` is identical to the condition (or its negation).\n\n#### Incorrect\n\n```ts\nconst isEligible = age >= 18 ? true : false;\nconst isBlocked = isAdmin ? false : true;\n```\n\n#### Correct\n\n```ts\nconst isEligible = age >= 18;\nconst isBlocked = !isAdmin;\n```\n\n### Pattern 4 โ If/else returning or assigning boolean literals\n\nWhen both branches of an `if`/`else` exclusively `return` or assign the same variable to a boolean literal, the entire construct reduces to a single expression.\n\n#### Incorrect\n\n```ts\nif (items.length > 0) {\n return true;\n} else {\n return false;\n}\n\nlet isValid;\nif (age >= 18) {\n isValid = true;\n} else {\n isValid = false;\n}\n```\n\n#### Correct\n\n```ts\nreturn items.length > 0;\nconst isValid = age >= 18;\n```\n\n## Out of Scope\n\n- De Morgan transformations (`!(a && b)` โ `!a || !b`) โ too subjective\n- `!!value` double-negation โ intentional type-coercion pattern\n- Loose equality (`== true`) โ different semantics\n- Complex boolean simplification โ requires symbolic reasoning\n\n## Error Messages\n\nEach pattern has a distinct `messageId`:\n\n| Pattern | `messageId` |\n| ------- | ---------------------------- |\n| 1 | `redundantBooleanComparison` |\n| 2 | `unnecessaryElse` |\n| 3 | `ternaryBooleanLiteral` |\n| 4 | `ifElseBooleanLiteral` |\n\nAll four messages follow the standard what/why/how format.\n\n## Suggestions\n\nAll four patterns provide suggestions (not auto-fixes) โ the transformations are safe but the developer should confirm intent before applying.\n",
|
|
28
29
|
"no-swallowed-errors": "# llm-core/no-swallowed-errors\n\n๐ Disallow catch blocks that only log to console and swallow the error.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, ๐ `best-practices`, โ
`recommended`.\n\n<!-- end auto-generated rule header -->\n\nDisallow `catch` blocks that only call `console.log`, `console.warn`, `console.error`, or `console.debug` without rethrowing, returning, or delegating the failure to a real error handler.\n\n## Rule Details\n\nLLMs often generate placeholder error handling like `catch (error) { console.error(error); }`. That looks intentional, but it still swallows the failure: callers do not see an error, control flow continues, and production systems quietly drift into bad state.\n\nThis rule focuses on the narrow, high-signal case where a non-empty `catch` block contains **only console logging calls**. It deliberately does **not** overlap with `no-empty-catch` โ truly empty or comment-only blocks belong to that rule.\n\n## Examples\n\n### Incorrect\n\n```ts\ntry {\n await processOrder(order);\n} catch (error) {\n console.error(error);\n}\n\ntry {\n await loadConfig();\n} catch (error) {\n console.warn(\"Config failed\", error);\n console.debug(error);\n}\n```\n\n### Correct\n\n```ts\ntry {\n await processOrder(order);\n} catch (error) {\n throw new Error(\"Failed to process order\", { cause: error });\n}\n\ntry {\n return await loadConfig();\n} catch (error) {\n logger.error(\"Config load failed\", { error });\n return null;\n}\n\ntry {\n await publishEvent(event);\n} catch (error) {\n Sentry.captureException(error);\n}\n\ntry {\n await performWork();\n} catch (error) {\n console.error(error);\n throw error;\n}\n```\n\n## What This Rule Flags\n\n| Catch body contents | Flagged? |\n| ----------------------------------------------- | -------- |\n| `console.error(error)` | โ
Yes |\n| `console.log(error); console.warn(\"failed\", e)` | โ
Yes |\n| `console.error(error); throw error;` | โ No |\n| `console.error(error); handleError(error);` | โ No |\n| `handleError(error)` | โ No |\n| empty `catch {}` | โ No |\n\n## Why Console-Only Handling Is Risky\n\n- Logging alone does not change control flow.\n- Callers cannot recover because they never learn the operation failed.\n- Background tasks can keep running with partial or invalid state.\n- The code looks \"handled\" in review even though the failure was dropped.\n\n## Error Messages\n\nThe teaching message explains:\n\n1. **What's wrong** โ the catch block only logs and swallows the error\n2. **Why** โ execution continues as if nothing failed\n3. **How to fix** โ rethrow, return an explicit fallback, or delegate to a real handler such as a logger or error tracker\n",
|
|
29
30
|
"no-type-assertion-any": "# llm-core/no-type-assertion-any\n\n๐ Disallow type assertions to `any` that bypass TypeScript's type safety.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, โ
`recommended`, โจ๏ธ `typescript`.\n\n<!-- end auto-generated rule header -->\n\nDisallow type assertions to `any` (`as any` and `<any>` syntax).\n\n## Rule Details\n\nLLMs reach for `as any` as the default escape hatch when types don't align. This completely disables TypeScript's type checking at the assertion site and for every downstream usage of the value. It is the single most common way generated code defeats type safety.\n\n## Examples\n\n### Incorrect\n\n```ts\n// Bypasses all type checking\nconst result = data as any;\n\n// Silently accesses potentially nonexistent property\n(response as any).body;\n\n// Hides a type incompatibility\nprocess(input as any);\n\n// Angle bracket syntax (same problem)\nconst value = <any>data;\n```\n\n### Correct\n\n```ts\n// Assert to a specific known type\nconst result = data as ExpectedType;\n\n// Double assertion through unknown (explicit escape hatch)\nconst result = data as unknown as ExpectedType;\n\n// Use unknown and narrow with type guards\nfunction process(data: unknown) {\n if (typeof data === \"string\") {\n handle(data); // TypeScript knows it's a string\n }\n}\n\n// Properly type the response\nconst body = (response as ResponseWithBody).body;\n```\n\n## What This Rule Catches\n\nThe rule flags both forms of type assertion to `any`:\n\n1. **`as any`** โ `value as any`\n2. **`<any>`** โ `<any>value` (angle bracket syntax)\n\n### What This Rule Does NOT Catch\n\n- `any` in type annotations (`const x: any`) โ use `@typescript-eslint/no-explicit-any` for this\n- `any` in generic type arguments (`Array<any>`) โ use `llm-core/no-any-in-generic` for this\n- Implicit `any` from missing type annotations โ use `@typescript-eslint/no-unsafe-*` rules for this\n\n## Error Messages\n\nThe error message teaches the proper alternative:\n\n1. **What's wrong** โ the assertion bypasses all type checking\n2. **Why** โ `any` disables TypeScript's safety and leaks into downstream code\n3. **How to fix** โ assert to a specific type, or use `unknown` with type guards\n",
|
|
31
|
+
"no-unbounded-promise-all": "# llm-core/no-unbounded-promise-all\n\n๐ Disallow Promise.all fan-out over arbitrary collections without an explicit concurrency bound.\n\n๐ผ This rule is enabled in the ๐ `all` config.\n\n<!-- end auto-generated rule header -->\n\nDisallow `Promise.all(collection.map(...))` and `Promise.allSettled(collection.map(...))` fan-out over arbitrary collections unless the work is explicitly bounded.\n\nLLM-generated code often reaches for `Promise.all(items.map(...))` as a generic performance improvement. That is safe for small fixed tuples, but dangerous for user-sized arrays, database records, API pages, queues, and other arbitrary collections because it starts all work at once.\n\n## Rule Details\n\nThis rule reports obvious unbounded Promise fan-out patterns:\n\n- `Promise.all(items.map(...))`\n- `Promise.allSettled(items.map(...))`\n- `Promise.all(Array.from(items).map(...))`\n- `const jobs = items.map(...); await Promise.all(jobs)`\n\nIt intentionally allows common bounded alternatives:\n\n- small literal arrays such as `Promise.all([loadUser(), loadSettings()])`\n- `.map(...)` over literal tuples\n- callbacks wrapped in a limiter such as `limit(() => work(item))`\n- explicit batching, for example a `for...of` loop over `chunks(items, 10)`\n- sequential `for...of` loops when backpressure or ordering matters\n\n## Examples\n\n### Incorrect\n\n```ts\n// Starts one email send per user immediately.\nawait Promise.all(users.map((user) => sendEmail(user)));\n```\n\n```ts\n// allSettled still starts every item at once.\nawait Promise.allSettled(records.map((record) => processRecord(record)));\n```\n\n```ts\n// Storing the mapped promises does not make the fan-out bounded.\nconst jobs = Array.from(ids).map((id) => fetchUser(id));\nawait Promise.all(jobs);\n```\n\n### Correct\n\n```ts\n// Small fixed fan-out is bounded by the literal array size.\nconst [user, settings] = await Promise.all([\n fetchUser(userId),\n fetchSettings(userId),\n]);\n```\n\n```ts\n// Explicit concurrency limit.\nconst limit = pLimit(5);\nawait Promise.all(users.map((user) => limit(() => sendEmail(user))));\n```\n\n```ts\n// Explicit batching.\nfor (const batch of chunks(users, 10)) {\n await Promise.all(batch.map((user) => sendEmail(user)));\n}\n```\n\n```ts\n// Sequential backpressure.\nfor (const user of users) {\n await sendEmail(user);\n}\n```\n\n## What Counts as Unbounded Fan-Out\n\n| Pattern | Triggers? |\n| ------------------------------------------------------------------------------------- | --------- |\n| `Promise.all(users.map(sendEmail))` | Yes |\n| `Promise.allSettled(items.map(syncItem))` | Yes |\n| `Promise.all(Array.from(ids).map(fetchUser))` | Yes |\n| `const jobs = users.map(sendEmail); await Promise.all(jobs)` | Yes |\n| `Promise.all([fetchUser(id), fetchSettings(id)])` | No |\n| `Promise.all([1, 2, 3].map(fetchUser))` | No |\n| `Promise.all(users.map((user) => limit(() => sendEmail(user))))` | No |\n| `for (const batch of chunks(users, 10)) { await Promise.all(batch.map(sendEmail)); }` | No |\n\n## Error Messages\n\nThe error message teaches:\n\n1. **What's wrong** โ a collection is being fanned out without a concurrency bound\n2. **Why** โ large inputs can overload memory, APIs, or database pools\n3. **How to fix** โ use `p-limit`, batching, or a sequential loop depending on the intended backpressure\n",
|
|
30
32
|
"prefer-early-return": "# llm-core/prefer-early-return\n\n๐ Enforce guard clauses (early returns) instead of wrapping function bodies in a single if statement.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, โ
`recommended`, ๐จ `style`.\n\n<!-- end auto-generated rule header -->\n\nEnforce guard clauses (early returns) instead of wrapping function bodies in a single if statement.\n\n## Rule Details\n\nLLMs consistently wrap entire function bodies in a single `if` statement instead of using guard clauses. This creates unnecessary nesting and obscures the main logic. Guard clauses handle edge cases at the top of the function, leaving the \"happy path\" at the base indentation level.\n\nThis rule complements `max-nesting-depth` by teaching the specific pattern that prevents deep nesting in the first place.\n\n## Examples\n\n### Incorrect\n\n```ts\n// Entire body wrapped in if โ should use guard clause\nfunction process(data: string) {\n if (isValid(data)) {\n transform(data);\n save(data);\n }\n}\n\n// If/else where else is a simple throw โ invert to guard\nfunction validate(input: string) {\n if (input.length > 0) {\n parse(input);\n process(input);\n } else {\n throw new Error(\"empty input\");\n }\n}\n\n// Arrow function with wrapped body\nconst fetchUser = async (id: string) => {\n if (id) {\n const user = await db.find(id);\n return user;\n }\n};\n```\n\n### Correct\n\n```ts\n// Guard clause โ early return for the edge case\nfunction process(data: string) {\n if (!isValid(data)) return;\n transform(data);\n save(data);\n}\n\n// Guard clause โ early throw\nfunction validate(input: string) {\n if (input.length === 0) throw new Error(\"empty input\");\n parse(input);\n process(input);\n}\n\n// Guard clause in arrow function\nconst fetchUser = async (id: string) => {\n if (!id) return;\n const user = await db.find(id);\n return user;\n};\n```\n\n## What This Rule Catches\n\nThe rule flags functions where:\n\n1. The **only statement** in the function body is an `if` statement\n2. The `if` body contains at least `minBodyStatements` statements (default: 2)\n3. There is **no else**, or the else is a **single return/throw**\n\n### What This Rule Does NOT Catch\n\n- Functions with multiple statements before the `if` (only the wrapping pattern)\n- `if/else` where both branches have substantial logic (genuine branching)\n- `if/else if` chains (multiple conditions, not a simple guard)\n- `if` bodies with fewer statements than the `minBodyStatements` threshold\n\n## Options\n\n### `minBodyStatements`\n\nMinimum number of statements in the `if` body to trigger the rule. Default: `2`.\n\nSetting this to `1` catches even simple cases like `if (x) { doSomething(); }`. Setting it higher reduces noise for shorter functions.\n\n```json\n{ \"llm-core/prefer-early-return\": [\"error\", { \"minBodyStatements\": 3 }] }\n```\n\n## Error Messages\n\nThe error message teaches the guard clause pattern:\n\n1. **What's wrong** โ the function body is wrapped in a single `if`\n2. **Why** โ unnecessary nesting obscures the main logic\n3. **How to fix** โ concrete before/after showing the inverted condition with early return\n",
|
|
31
33
|
"prefer-nullish-coalescing": "# llm-core/prefer-nullish-coalescing\n\n๐ Prefer nullish coalescing over logical OR when providing default values.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, โ
`recommended`, ๐จ `style`.\n\n๐ก This rule is manually fixable by [editor suggestions](https://eslint.org/docs/latest/use/core-concepts#rule-suggestions).\n\n<!-- end auto-generated rule header -->\n\nPrefer `??` over `||` when providing fallback values so valid falsy values are preserved.\n\n## Rule Details\n\n`||` treats `0`, `\"\"`, and `false` as missing values. When code is selecting a default value, `??` is usually safer because it only falls back for `null` or `undefined`.\n\nThis rule uses syntax-only heuristics. It reports likely default-value expressions and intentionally skips common boolean logic patterns, including boolean contexts and boolean-like names such as `isReady`, `hasAccess`, or `canRetry`.\n\n## Examples\n\n### Incorrect\n\n```ts\nconst name = input || \"Unknown\";\nconst count = value || 10;\noptions.timeout = options.timeout || 5000;\nreturn cachedValue || computeDefault();\n```\n\n### Correct\n\n```ts\nconst name = input ?? \"Unknown\";\nconst count = value ?? 10;\noptions.timeout = options.timeout ?? 5000;\nreturn cachedValue ?? computeDefault();\n```\n\n### Not Reported\n\n```ts\nif (isReady || isForced) {\n run();\n}\n\nreturn flags.isReady || computeDefault();\nconst enabled = config.enabled || false;\nconst value = input || cached || \"fallback\";\n```\n\n## Limitations\n\nThis rule does not use type information. It avoids some obvious boolean false positives, but it cannot know the runtime type of every expression. It also skips chained logical expressions where a safe suggestion would require restructuring parentheses or converting the whole chain.\n",
|
|
32
34
|
"prefer-unknown-in-catch": "# llm-core/prefer-unknown-in-catch\n\n๐ Disallow `any` type annotation on catch clause parameters; prefer `unknown`.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, โ
`recommended`, โจ๏ธ `typescript`.\n\n<!-- end auto-generated rule header -->\n\nDisallow `catch (e: any)` โ use `catch (e: unknown)` and narrow before accessing properties.\n\n## Rule Details\n\nLLMs often generate `catch (e: any)` to suppress TypeScript errors on `e.message` or `e.stack`. This defeats TypeScript's type safety entirely for that variable: you can pass it to typed functions, access non-existent properties, and trigger runtime errors with no compile-time warning.\n\nSince TypeScript 4.0, `useUnknownInCatchVariables` (enabled by `strict`) makes catch parameters `unknown` by default. Explicitly annotating `any` overrides this protection.\n\nThis rule only targets catch clause parameters, not general `any` usage elsewhere. It complements `@typescript-eslint/no-explicit-any` without duplicating it.\n\n## Examples\n\n### Incorrect\n\n```ts\ntry {\n await fetchData();\n} catch (e: any) {\n // e.message compiles but is unsafe โ e might not be an Error\n console.error(e.message);\n}\n```\n\n### Correct\n\n```ts\n// Unknown + instanceof narrowing โ safe\ntry {\n await fetchData();\n} catch (e: unknown) {\n if (e instanceof Error) {\n console.error(e.message);\n } else {\n console.error(String(e));\n }\n}\n\n// No annotation needed (TS infers unknown under strict mode)\ntry {\n await fetchData();\n} catch (e) {\n if (e instanceof Error) console.error(e.message);\n}\n\n// Reusable utility\nfunction toError(e: unknown): Error {\n return e instanceof Error ? e : new Error(String(e));\n}\n\ntry {\n await fetchData();\n} catch (e) {\n logger.error(toError(e));\n}\n```\n\n## What This Rule Does NOT Flag\n\n- `any` in function parameters, generics, or type aliases โ those are outside this rule's scope\n- Catch parameters with no annotation โ TS's own `useUnknownInCatchVariables` handles that\n- `catch (e: unknown)` โ that is the correct pattern\n\n## Error Messages\n\nThe error message teaches:\n\n1. **What's wrong** โ `any` disables type-safety for the caught value\n2. **Why** โ TS 4.0 made this `unknown` by default for good reason\n3. **How to fix** โ use `unknown` with `instanceof Error` narrowing or a `toError` helper\n",
|
|
@@ -34,5 +36,5 @@ export const embeddedDocs = {
|
|
|
34
36
|
"throw-error-objects": "# llm-core/throw-error-objects\n\n๐ Disallow throwing non-Error values such as strings, template literals, plain objects, or arrays.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, ๐ `best-practices`, โ
`recommended`.\n\n<!-- end auto-generated rule header -->\n\nDisallow throwing string literals, template literals, plain objects, arrays, or other non-Error values.\n\n## Rule Details\n\nLLMs often generate `throw \"something went wrong\"` or `throw { code: 404 }` as a shorthand. These patterns lose the stack trace, break `e instanceof Error` checks, and cause silent failures in logging and error-reporting tools that expect an `Error` object.\n\nThis is a syntax-only rule and does not require type information. It allows `throw` of identifiers, member expressions, call expressions, and `new` expressions because it cannot statically prove their type โ those forms are assumed to be Error instances or safe wrappers.\n\n## Examples\n\n### Incorrect\n\n```ts\n// String literal โ no stack trace\nthrow \"something went wrong\";\n\n// Template literal โ still no stack trace\nthrow `failed to connect to ${host}`;\n\n// Plain object โ instanceof Error fails, .stack is undefined\nthrow { code: 404, message: \"not found\" };\n\n// Array โ completely wrong type\nthrow [\"validation\", \"failed\"];\n\n// Number\nthrow 500;\n```\n\n### Correct\n\n```ts\n// Error instance โ stack trace, instanceof, .message all work\nthrow new Error(\"something went wrong\");\n\n// Error subclass\nthrow new ValidationError(\"invalid input\");\n\n// Identifier โ may hold an Error, allowed\nthrow err;\n\n// Call expression โ assumed to create a proper Error\nthrow createError(\"context\", { cause: err });\n\n// Enrich an existing error with context\nthrow Object.assign(new Error(\"not found\"), { code: 404 });\n```\n\n## What This Rule Does NOT Flag\n\n- `throw identifier` โ the identifier may hold an Error; type-checking would be needed to verify\n- `throw expr.property` โ same reason\n- `throw callExpression()` โ assumed to return an Error\n- `throw new SomeThing()` โ assumed to construct an Error\n\n## Error Messages\n\nThe error message teaches:\n\n1. **What's wrong** โ the thrown value is not an Error instance\n2. **Why** โ stack traces are lost, catch handlers receive unexpected types\n3. **How to fix** โ `new Error(msg)`, `Object.assign(new Error(...), extras)`, or Error subclasses\n",
|
|
35
37
|
"uninvoked-array-callback": "# llm-core/uninvoked-array-callback\n\n๐ Disallow callbacks on sparse arrays created with Array(length) because holes skip callback invocation.\n\n๐ผ This rule is enabled in the following configs: ๐ `all`, ๐ `best-practices`, โ
`recommended`.\n\n<!-- end auto-generated rule header -->\n\n## Rule details\n\nThis rule flags array callback methods called directly on sparse arrays created with `Array(length)` or `new Array(length)`. Those constructors create holes, not present `undefined` elements. JavaScript array callback methods skip holes, so callbacks such as `.map(...)`, `.forEach(...)`, `.filter(...)`, `.some(...)`, and `.every(...)` may run zero times even though the code looks like it should run once per index.\n\nLLMs often generate this pattern when they want to create `n` rows, placeholders, tasks, or test cases. The code silently returns another sparse array or performs no side effects.\n\nFlagged patterns:\n\n```ts\nconst rows = new Array(5).map((_, index) => createRow(index));\n\nArray(count).forEach((_, index) => {\n save(index);\n});\n\nconst ids = new Array(3).map((_, index) => index).filter((index) => index > 0);\n```\n\nCorrect patterns:\n\n```ts\nconst rows = Array.from({ length: 5 }, (_, index) => createRow(index));\n\nnew Array(count).fill(null).forEach((_, index) => {\n save(index);\n});\n\nconst ids = [...new Array(3)]\n .map((_, index) => index)\n .filter((index) => index > 0);\n```\n\n## What counts as a sparse array callback\n\n| Pattern | Triggers? | Why |\n| --------------------------------------- | --------- | ----------------------------------------------------------- |\n| `new Array(5).map(callback)` | Yes | Length-only arrays contain holes, so callbacks are skipped. |\n| `Array(count).forEach(callback)` | Yes | `Array(length)` has the same sparse-array behavior. |\n| `new Array(5).fill(null).map(callback)` | No | `.fill(...)` materializes present elements first. |\n| `new Array(5).fill(null, 1).map(cb)` | Yes | Partial fills leave holes outside the filled range. |\n| `[...new Array(5)].map(callback)` | No | Spreading materializes present `undefined` elements. |\n| `Array.from({ length: 5 }, callback)` | No | `Array.from` invokes the mapping callback for each index. |\n| `new Array(\"a\", \"b\").map(callback)` | No | Multiple arguments create present elements. |\n| `Array(true).map(callback)` | No | Non-number single arguments create one present element. |\n| `collection.map(callback)` | No | The rule stays narrow and only targets Array constructors. |\n\n## Error messages\n\nThe error message teaches:\n\n1. **What's wrong** โ `Array(length)` created sparse slots, so the callback will not run for them.\n2. **Why** โ LLM-generated code often expects one callback invocation per index, but array methods skip holes.\n3. **How to fix** โ use `Array.from({ length }, mapper)` or materialize elements with `.fill(...)` before calling callback methods.\n",
|
|
36
38
|
};
|
|
37
|
-
export const ruleNames = ["bad-comparison-sequence", "bad-min-max-func", "consistent-catch-param-name", "explicit-export-types", "filename-match-export", "max-complexity", "max-file-length", "max-function-length", "max-nesting-depth", "max-params", "missing-throw", "naming-conventions", "no-any-in-generic", "no-async-array-callbacks", "no-async-promise-executor", "no-commented-out-code", "no-empty-catch", "no-exported-function-expressions", "no-floating-promise", "no-hallucinated-local-imports", "no-incorrect-sort", "no-inline-disable", "no-llm-artifacts", "no-magic-numbers", "no-redundant-logic", "no-swallowed-errors", "no-type-assertion-any", "prefer-early-return", "prefer-nullish-coalescing", "prefer-unknown-in-catch", "structured-logging", "throw-error-objects", "uninvoked-array-callback"];
|
|
39
|
+
export const ruleNames = ["bad-comparison-sequence", "bad-min-max-func", "consistent-catch-param-name", "explicit-export-types", "filename-match-export", "max-complexity", "max-file-length", "max-function-length", "max-nesting-depth", "max-params", "missing-throw", "naming-conventions", "no-any-in-generic", "no-async-array-callbacks", "no-async-promise-executor", "no-commented-out-code", "no-empty-catch", "no-exported-function-expressions", "no-floating-promise", "no-hallucinated-local-imports", "no-hallucinated-package-imports", "no-incorrect-sort", "no-inline-disable", "no-llm-artifacts", "no-magic-numbers", "no-redundant-logic", "no-swallowed-errors", "no-type-assertion-any", "no-unbounded-promise-all", "prefer-early-return", "prefer-nullish-coalescing", "prefer-unknown-in-catch", "structured-logging", "throw-error-objects", "uninvoked-array-callback"];
|
|
38
40
|
//# sourceMappingURL=embedded-docs.js.map
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"embedded-docs.js","sourceRoot":"","sources":["../src/embedded-docs.ts"],"names":[],"mappings":"AAAA,sEAAsE;AAEtE,MAAM,CAAC,MAAM,YAAY,GAA2B;IAClD,yBAAyB,EAAE,yyEAAyyE;IACp0E,kBAAkB,EAAE,6oFAA6oF;IACjqF,6BAA6B,EAAE,ipGAAipG;IAChrG,uBAAuB,EAAE,slLAAslL;IAC/mL,uBAAuB,EAAE,8qFAA8qF;IACvsF,gBAAgB,EAAE,8mHAA8mH;IAChoH,iBAAiB,EAAE,wrEAAwrE;IAC3sE,qBAAqB,EAAE,ksEAAksE;IACztE,mBAAmB,EAAE,+qEAA+qE;IACpsE,YAAY,EAAE,i8EAAi8E;IAC/8E,eAAe,EAAE,2vDAA2vD;IAC5wD,oBAAoB,EAAE,0sDAA0sD;IAChuD,mBAAmB,EAAE,srFAAsrF;IAC3sF,0BAA0B,EAAE,yyHAAyyH;IACr0H,2BAA2B,EAAE,ooEAAooE;IACjqE,uBAAuB,EAAE,8kGAA8kG;IACvmG,gBAAgB,EAAE,kxFAAkxF;IACpyF,kCAAkC,EAAE,6/HAA6/H;IACjiI,qBAAqB,EAAE,4iHAA4iH;IACnkH,+BAA+B,EAAE,qhFAAqhF;IACtjF,mBAAmB,EAAE,gwDAAgwD;IACrxD,mBAAmB,EAAE,w7DAAw7D;IAC78D,kBAAkB,EAAE,63HAA63H;IACj5H,kBAAkB,EAAE,o5GAAo5G;IACx6G,oBAAoB,EAAE,g1HAAg1H;IACt2H,qBAAqB,EAAE,kyFAAkyF;IACzzF,uBAAuB,EAAE,oqEAAoqE;IAC7rE,qBAAqB,EAAE,8mGAA8mG;IACroG,2BAA2B,EAAE,kwDAAkwD;IAC/xD,yBAAyB,EAAE,uzEAAuzE;IACl1E,oBAAoB,EAAE,6hGAA6hG;IACnjG,qBAAqB,EAAE,+2EAA+2E;IACt4E,0BAA0B,EAAE,4nGAA4nG;CACzpG,CAAC;AAEF,MAAM,CAAC,MAAM,SAAS,GAAa,CAAC,yBAAyB,EAAC,kBAAkB,EAAC,6BAA6B,EAAC,uBAAuB,EAAC,uBAAuB,EAAC,gBAAgB,EAAC,iBAAiB,EAAC,qBAAqB,EAAC,mBAAmB,EAAC,YAAY,EAAC,eAAe,EAAC,oBAAoB,EAAC,mBAAmB,EAAC,0BAA0B,EAAC,2BAA2B,EAAC,uBAAuB,EAAC,gBAAgB,EAAC,kCAAkC,EAAC,qBAAqB,EAAC,+BAA+B,EAAC,mBAAmB,EAAC,mBAAmB,EAAC,kBAAkB,EAAC,kBAAkB,EAAC,oBAAoB,EAAC,qBAAqB,EAAC,uBAAuB,EAAC,qBAAqB,EAAC,2BAA2B,EAAC,yBAAyB,EAAC,oBAAoB,EAAC,qBAAqB,EAAC,0BAA0B,CAAC,CAAC"}
|
|
1
|
+
{"version":3,"file":"embedded-docs.js","sourceRoot":"","sources":["../src/embedded-docs.ts"],"names":[],"mappings":"AAAA,sEAAsE;AAEtE,MAAM,CAAC,MAAM,YAAY,GAA2B;IAClD,yBAAyB,EAAE,yyEAAyyE;IACp0E,kBAAkB,EAAE,6oFAA6oF;IACjqF,6BAA6B,EAAE,ipGAAipG;IAChrG,uBAAuB,EAAE,slLAAslL;IAC/mL,uBAAuB,EAAE,8qFAA8qF;IACvsF,gBAAgB,EAAE,8mHAA8mH;IAChoH,iBAAiB,EAAE,wrEAAwrE;IAC3sE,qBAAqB,EAAE,ksEAAksE;IACztE,mBAAmB,EAAE,+qEAA+qE;IACpsE,YAAY,EAAE,i8EAAi8E;IAC/8E,eAAe,EAAE,2vDAA2vD;IAC5wD,oBAAoB,EAAE,0sDAA0sD;IAChuD,mBAAmB,EAAE,srFAAsrF;IAC3sF,0BAA0B,EAAE,yyHAAyyH;IACr0H,2BAA2B,EAAE,ooEAAooE;IACjqE,uBAAuB,EAAE,8kGAA8kG;IACvmG,gBAAgB,EAAE,kxFAAkxF;IACpyF,kCAAkC,EAAE,6/HAA6/H;IACjiI,qBAAqB,EAAE,4iHAA4iH;IACnkH,+BAA+B,EAAE,qhFAAqhF;IACtjF,iCAAiC,EAAE,yiKAAyiK;IAC5kK,mBAAmB,EAAE,gwDAAgwD;IACrxD,mBAAmB,EAAE,w7DAAw7D;IAC78D,kBAAkB,EAAE,63HAA63H;IACj5H,kBAAkB,EAAE,o5GAAo5G;IACx6G,oBAAoB,EAAE,g1HAAg1H;IACt2H,qBAAqB,EAAE,kyFAAkyF;IACzzF,uBAAuB,EAAE,oqEAAoqE;IAC7rE,0BAA0B,EAAE,qqHAAqqH;IACjsH,qBAAqB,EAAE,8mGAA8mG;IACroG,2BAA2B,EAAE,kwDAAkwD;IAC/xD,yBAAyB,EAAE,uzEAAuzE;IACl1E,oBAAoB,EAAE,6hGAA6hG;IACnjG,qBAAqB,EAAE,+2EAA+2E;IACt4E,0BAA0B,EAAE,4nGAA4nG;CACzpG,CAAC;AAEF,MAAM,CAAC,MAAM,SAAS,GAAa,CAAC,yBAAyB,EAAC,kBAAkB,EAAC,6BAA6B,EAAC,uBAAuB,EAAC,uBAAuB,EAAC,gBAAgB,EAAC,iBAAiB,EAAC,qBAAqB,EAAC,mBAAmB,EAAC,YAAY,EAAC,eAAe,EAAC,oBAAoB,EAAC,mBAAmB,EAAC,0BAA0B,EAAC,2BAA2B,EAAC,uBAAuB,EAAC,gBAAgB,EAAC,kCAAkC,EAAC,qBAAqB,EAAC,+BAA+B,EAAC,iCAAiC,EAAC,mBAAmB,EAAC,mBAAmB,EAAC,kBAAkB,EAAC,kBAAkB,EAAC,oBAAoB,EAAC,qBAAqB,EAAC,uBAAuB,EAAC,0BAA0B,EAAC,qBAAqB,EAAC,2BAA2B,EAAC,yBAAyB,EAAC,oBAAoB,EAAC,qBAAqB,EAAC,0BAA0B,CAAC,CAAC"}
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"rule-data.d.ts","sourceRoot":"","sources":["../../src/resources/rule-data.ts"],"names":[],"mappings":"AAGA,KAAK,YAAY,GACb,YAAY,GACZ,YAAY,GACZ,gBAAgB,GAChB,OAAO,GACP,SAAS,CAAC;AAEd,UAAU,aAAa;IACrB,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,cAAc,EAAE,OAAO,CAAC;IACxB,QAAQ,EAAE,YAAY,CAAC;CACxB;
|
|
1
|
+
{"version":3,"file":"rule-data.d.ts","sourceRoot":"","sources":["../../src/resources/rule-data.ts"],"names":[],"mappings":"AAGA,KAAK,YAAY,GACb,YAAY,GACZ,YAAY,GACZ,gBAAgB,GAChB,OAAO,GACP,SAAS,CAAC;AAEd,UAAU,aAAa;IACrB,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,cAAc,EAAE,OAAO,CAAC;IACxB,QAAQ,EAAE,YAAY,CAAC;CACxB;AAyDD,wBAAgB,YAAY,IAAI,MAAM,EAAE,CAIvC;AAED,wBAAgB,kBAAkB,IAAI,aAAa,EAAE,CAcpD;AAED,wBAAgB,iBAAiB,CAC/B,OAAO,EAAE,aAAa,EAAE,GACvB,MAAM,CAAC,YAAY,EAAE,MAAM,CAAC,CAY9B"}
|
|
@@ -12,7 +12,9 @@ const CATEGORY_CONFIGS = [
|
|
|
12
12
|
// MCP resource still needs one of the public category labels for every rule.
|
|
13
13
|
const ALL_ONLY_RULE_CATEGORIES = {
|
|
14
14
|
"no-hallucinated-local-imports": "hygiene",
|
|
15
|
+
"no-hallucinated-package-imports": "hygiene",
|
|
15
16
|
"no-incorrect-sort": "best-practices",
|
|
17
|
+
"no-unbounded-promise-all": "best-practices",
|
|
16
18
|
};
|
|
17
19
|
function bareRuleId(ruleId) {
|
|
18
20
|
return ruleId.replace(/^llm-core\//, "");
|
|
@@ -1 +1 @@
|
|
|
1
|
-
{"version":3,"file":"rule-data.js","sourceRoot":"","sources":["../../src/resources/rule-data.ts"],"names":[],"mappings":"AAAA,OAAO,MAAM,MAAM,wBAAwB,CAAC;AAC5C,OAAO,EAAE,kBAAkB,EAAE,MAAM,qCAAqC,CAAC;AAiCzE,MAAM,aAAa,GAAG,MAA+B,CAAC;AAEtD,MAAM,gBAAgB,GAAmB;IACvC,YAAY;IACZ,YAAY;IACZ,gBAAgB;IAChB,OAAO;IACP,SAAS;CACV,CAAC;AAEF,+EAA+E;AAC/E,6EAA6E;AAC7E,MAAM,wBAAwB,GAAiC;IAC7D,+BAA+B,EAAE,SAAS;IAC1C,mBAAmB,EAAE,gBAAgB;
|
|
1
|
+
{"version":3,"file":"rule-data.js","sourceRoot":"","sources":["../../src/resources/rule-data.ts"],"names":[],"mappings":"AAAA,OAAO,MAAM,MAAM,wBAAwB,CAAC;AAC5C,OAAO,EAAE,kBAAkB,EAAE,MAAM,qCAAqC,CAAC;AAiCzE,MAAM,aAAa,GAAG,MAA+B,CAAC;AAEtD,MAAM,gBAAgB,GAAmB;IACvC,YAAY;IACZ,YAAY;IACZ,gBAAgB;IAChB,OAAO;IACP,SAAS;CACV,CAAC;AAEF,+EAA+E;AAC/E,6EAA6E;AAC7E,MAAM,wBAAwB,GAAiC;IAC7D,+BAA+B,EAAE,SAAS;IAC1C,iCAAiC,EAAE,SAAS;IAC5C,mBAAmB,EAAE,gBAAgB;IACrC,0BAA0B,EAAE,gBAAgB;CAC7C,CAAC;AAEF,SAAS,UAAU,CAAC,MAAc;IAChC,OAAO,MAAM,CAAC,OAAO,CAAC,aAAa,EAAE,EAAE,CAAC,CAAC;AAC3C,CAAC;AAED,SAAS,aAAa,CAAC,UAAwB;IAC7C,OAAO,IAAI,GAAG,CACZ,CAAC,aAAa,CAAC,OAAO,CAAC,UAAU,CAAC,IAAI,EAAE,CAAC;SACtC,OAAO,CAAC,CAAC,MAAM,EAAE,EAAE,CAAC,MAAM,CAAC,IAAI,CAAC,MAAM,CAAC,KAAK,IAAI,EAAE,CAAC,CAAC;SACpD,GAAG,CAAC,UAAU,CAAC,CACnB,CAAC;AACJ,CAAC;AAED,MAAM,cAAc,GAAG,IAAI,GAAG,CAAuB;IACnD,GAAG,gBAAgB,CAAC,OAAO,CAAC,CAAC,QAAQ,EAAE,EAAE,CACvC,CAAC,GAAG,aAAa,CAAC,QAAQ,CAAC,CAAC,CAAC,GAAG,CAAC,CAAC,QAAQ,EAAE,EAAE,CAAC,CAAC,QAAQ,EAAE,QAAQ,CAAC,CAAC,CACrE;IACD,GAAG,MAAM,CAAC,OAAO,CAAC,wBAAwB,CAAC;CACX,CAAC,CAAC;AAEpC,MAAM,UAAU,YAAY;IAC1B,OAAO,MAAM,CAAC,IAAI,CAAC,aAAa,CAAC,KAAK,CAAC,CAAC,IAAI,CAAC,CAAC,IAAI,EAAE,KAAK,EAAE,EAAE,CAC3D,IAAI,CAAC,aAAa,CAAC,KAAK,CAAC,CAC1B,CAAC;AACJ,CAAC;AAED,MAAM,UAAU,kBAAkB;IAChC,OAAO,YAAY,EAAE,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE;QACjC,MAAM,QAAQ,GAAG,cAAc,CAAC,GAAG,CAAC,IAAI,CAAC,CAAC;QAC1C,IAAI,CAAC,QAAQ,EAAE,CAAC;YACd,MAAM,IAAI,KAAK,CAAC,SAAS,IAAI,yCAAyC,CAAC,CAAC;QAC1E,CAAC;QAED,OAAO;YACL,IAAI;YACJ,WAAW,EAAE,aAAa,CAAC,KAAK,CAAC,IAAI,CAAC,EAAE,IAAI,EAAE,IAAI,EAAE,WAAW,IAAI,EAAE;YACrE,cAAc,EAAE,kBAAkB,CAAC,IAAI,CAAC,KAAK,SAAS;YACtD,QAAQ;SACT,CAAC;IACJ,CAAC,CAAC,CAAC;AACL,CAAC;AAED,MAAM,UAAU,iBAAiB,CAC/B,OAAwB;IAExB,OAAO;QACL,UAAU,EAAE,OAAO,CAAC,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,QAAQ,KAAK,YAAY,CAAC;aACnE,MAAM;QACT,UAAU,EAAE,OAAO,CAAC,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,QAAQ,KAAK,YAAY,CAAC;aACnE,MAAM;QACT,gBAAgB,EAAE,OAAO,CAAC,MAAM,CAC9B,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,QAAQ,KAAK,gBAAgB,CAC/C,CAAC,MAAM;QACR,KAAK,EAAE,OAAO,CAAC,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,QAAQ,KAAK,OAAO,CAAC,CAAC,MAAM;QACnE,OAAO,EAAE,OAAO,CAAC,MAAM,CAAC,CAAC,KAAK,EAAE,EAAE,CAAC,KAAK,CAAC,QAAQ,KAAK,SAAS,CAAC,CAAC,MAAM;KACxE,CAAC;AACJ,CAAC"}
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "eslint-plugin-llm-core-mcp",
|
|
3
|
-
"version": "0.27.
|
|
3
|
+
"version": "0.27.3",
|
|
4
4
|
"description": "MCP server for just-in-time linting guidance from eslint-plugin-llm-core",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"@modelcontextprotocol/sdk": "^1.29.0",
|
|
43
43
|
"@typescript-eslint/parser": "^8.0.0",
|
|
44
44
|
"eslint": "^10.1.0",
|
|
45
|
-
"eslint-plugin-llm-core": "0.
|
|
45
|
+
"eslint-plugin-llm-core": "0.29.0",
|
|
46
46
|
"zod": "^3.23.0"
|
|
47
47
|
},
|
|
48
48
|
"devDependencies": {
|