@blumintinc/eslint-plugin-blumint 1.20.39 → 1.20.40

package/lib/index.js

@@ -223,7 +223,7 @@ function noFrontendImportsFromFunctionsPatterns(pattern) {
 module.exports = {
     meta: {
         name: '@blumintinc/eslint-plugin-blumint',
-        version: '1.20.39',
+        version: '1.20.40',
     },
     parseOptions: {
         ecmaVersion: 2020,

package/lib/rules/avoid-utils-directory.js

@@ -21,6 +21,14 @@ exports.avoidUtilsDirectory = (0, createRule_1.createRule)({
     },
     defaultOptions: [],
     create(context) {
+        // Anchor the reported path at the directory ESLint was configured with,
+        // not the node process cwd. The two differ under the VS Code ESLint
+        // extension, in monorepos, and for any programmatic `new ESLint({ cwd })`,
+        // where reading the process cwd names the file by a path the reader cannot
+        // locate (issue #1475). The `typeof` guard keeps the rule working under
+        // harnesses that predate `getCwd`, matching the sibling rules that resolve
+        // a cwd.
+        const cwd = typeof context.getCwd === 'function' ? context.getCwd() : process.cwd();
         return {
             Program(node) {
                 // Normalize Windows backslash separators so the forward-slash `utils/`
@@ -28,8 +36,10 @@ exports.avoidUtilsDirectory = (0, createRule_1.createRule)({
                 // returns `C:\repo\src\utils\foo.ts` on Windows, the regex never
                 // matches, and the rule silently reports nothing (issue #1270).
                 const filename = context.getFilename().replace(/\\/g, '/');
+                // `|| filename` covers the case where the file IS the cwd (an empty
+                // relative path), keeping a usable path in the message.
                 const relativePath = path_1.default.isAbsolute(filename)
-                    ? path_1.default.relative(process.cwd(), filename) || filename
+                    ? path_1.default.relative(cwd, filename) || filename
                     : filename;
                 // Skip files in node_modules
                 if (filename.includes('node_modules')) {

package/lib/rules/enforce-assert-safe-object-key.js

@@ -71,31 +71,37 @@ exports.enforceAssertSafeObjectKey = (0, createRule_1.createRule)({
          */
         const isReportSuppressed = (0, disableDirectives_1.createSuppressionChecker)(context);
         /**
-         * Directory of the file being fixed, relative to the repo root, or null for
-         * virtual/stdin files (RuleTester default 'file.ts', '<input>', '<text>')
-         * whose non-absolute name cannot anchor a relative path.
+         * The directory ESLint itself was configured with, which is what
+         * `importPath` is anchored at. The node process cwd is only a fallback for
+         * harnesses that predate `getCwd`: the two differ under the VS Code ESLint
+         * extension, in monorepos, and for any programmatic `new ESLint({ cwd })`,
+         * and anchoring at the process cwd there emits an unresolvable specifier.
+         */
+        const cwd = typeof context.getCwd === 'function' ? context.getCwd() : process.cwd();
+        /**
+         * Directory of the file being fixed, relative to the configured cwd, or
+         * null for virtual/stdin files (RuleTester default 'file.ts', '<input>',
+         * '<text>') whose non-absolute name cannot anchor a relative path.
          */
         const fileDirFromRoot = () => {
             const rawFilename = context.getFilename().replace(/\\/g, '/');
             if (!path_1.default.isAbsolute(rawFilename)) {
                 return null;
             }
-            const fileRelToCwd = path_1.default
-                .relative(process.cwd(), rawFilename)
-                .replace(/\\/g, '/');
+            const fileRelToCwd = path_1.default.relative(cwd, rawFilename).replace(/\\/g, '/');
             return path_1.default.posix.dirname(fileRelToCwd);
         };
         /**
          * Computes the module specifier for the injected assertSafe import.
          *
-         * `importPath` is anchored at the repo root (relative to process.cwd(),
-         * which is the repo root in real eslint runs), matching how
-         * avoid-utils-directory and test-file-location-enforcement treat paths.
-         * A bare repo-root specifier such as 'functions/src/util/assertSafe' is
-         * unresolvable inside the functions/ TS project, whose baseUrl is
-         * functions/: it would resolve to functions/functions/src/util/assertSafe,
-         * which does not exist. The specifier is therefore derived relative to the
-         * file being fixed so the emitted import resolves from that file's location.
+         * `importPath` is anchored at the repo root — the directory ESLint runs
+         * with, not the node process cwd — matching how avoid-utils-directory and
+         * test-file-location-enforcement treat paths. A bare repo-root specifier
+         * such as 'functions/src/util/assertSafe' is unresolvable inside the
+         * functions/ TS project, whose baseUrl is functions/: it would resolve to
+         * functions/functions/src/util/assertSafe, which does not exist. The
+         * specifier is therefore derived relative to the file being fixed so the
+         * emitted import resolves from that file's location.
          */
         const computeImportSpecifier = () => {
             const fileDir = fileDirFromRoot();

package/lib/rules/enforce-dynamic-imports.d.ts

@@ -7,6 +7,19 @@ type Options = [
         allowImportType?: boolean;
     }
 ];
+/**
+ * A module this plugin injects on the user's behalf must be one the plugin's
+ * own default config accepts. Several rules in the recommended config write a
+ * *static* import as part of their autofix; without these entries `--fix`
+ * would trade an auto-fixable violation for a non-fixable one, and the
+ * suggested remedy is impossible for most of them anyway (hooks must be called
+ * unconditionally and decorators must resolve statically, so neither can be
+ * loaded dynamically).
+ *
+ * `src/tests/enforce-dynamic-imports.test.ts` derives the set of specifiers the
+ * fixers emit from the rule sources and asserts every external one is listed
+ * here, so a seventh injected module cannot slip in unlisted.
+ */
 export declare const DEFAULT_IGNORED_LIBRARIES: string[];
 export declare const DEFAULT_INTERNAL_PREFIXES: string[];
 declare const _default: import("@typescript-eslint/utils/dist/ts-eslint/Rule").RuleModule<"dynamicImportRequired", Options, import("@typescript-eslint/utils/dist/ts-eslint/Rule").RuleListener>;

package/lib/rules/enforce-dynamic-imports.js

@@ -5,6 +5,19 @@ const createRule_1 = require("../utils/createRule");
 const minimatch_1 = require("minimatch");
 const module_1 = require("module");
 exports.RULE_NAME = 'enforce-dynamic-imports';
+/**
+ * A module this plugin injects on the user's behalf must be one the plugin's
+ * own default config accepts. Several rules in the recommended config write a
+ * *static* import as part of their autofix; without these entries `--fix`
+ * would trade an auto-fixable violation for a non-fixable one, and the
+ * suggested remedy is impossible for most of them anyway (hooks must be called
+ * unconditionally and decorators must resolve statically, so neither can be
+ * loaded dynamically).
+ *
+ * `src/tests/enforce-dynamic-imports.test.ts` derives the set of specifiers the
+ * fixers emit from the rule sources and asserts every external one is listed
+ * here, so a seventh injected module cannot slip in unlisted.
+ */
 exports.DEFAULT_IGNORED_LIBRARIES = [
     'react',
     'react/**',
@@ -19,6 +32,13 @@ exports.DEFAULT_IGNORED_LIBRARIES = [
     '@emotion/**',
     'clsx',
     'tailwind-merge',
+    // Injected by this plugin's own fixers:
+    'use-latest-callback',
+    '@blumintinc/typescript-memoize',
+    '@blumintinc/use-deep-compare',
+    'microdiff',
+    'safe-stable-stringify',
+    'fast-deep-equal', // fast-deep-equal-over-microdiff
 ];
 exports.DEFAULT_INTERNAL_PREFIXES = ['src/', 'functions/'];
 // Pre-built set of Node.js core module names for O(1) lookup.

package/lib/rules/require-props-composition.js

@@ -838,7 +838,7 @@ function isNameDeclaredWithin(root, name) {
  * anything the parse cannot decide with certainty) still reports, so the rule
  * cannot be silently disabled by an unresolvable name.
  */
-function isPropLessImportedComponent(program, localName, filename, componentRoot) {
+function isPropLessImportedComponent(program, localName, filename, componentRoot, cwd) {
     const relativeImport = findRelativeImport(program, localName);
     if (!relativeImport) {
         return false;
@@ -849,9 +849,16 @@ function isPropLessImportedComponent(program, localName, filename, componentRoot
         return false;
     }
     try {
+        // A relative filename is anchored at the directory ESLint was configured
+        // with, never the node process cwd. The two differ under the VS Code ESLint
+        // extension, in monorepos, and for any programmatic `new Linter({ cwd })`,
+        // and anchoring at the process cwd there resolves the sibling import
+        // against the wrong directory: the child module is not found, the
+        // prop-less relaxation silently stops applying, and the parent reports a
+        // composition it cannot satisfy (issue #1476).
         const absolute = path_1.default.isAbsolute(filename)
             ? filename
-            : path_1.default.resolve(process.cwd(), filename);
+            : path_1.default.resolve(cwd, filename);
         const resolved = resolveRelativeModule(path_1.default.dirname(absolute), relativeImport.source);
         if (!resolved) {
             return false;
@@ -948,6 +955,11 @@ exports.requirePropsComposition = (0, createRule_1.createRule)({
         // `/src/`) so absolute POSIX and Windows paths both resolve (issue #1268).
         // Glob matching needs forward slashes, while resolving a relative import off
         // disk needs the platform-native path — keep both.
+        // Sibling modules are resolved from disk relative to the file under lint,
+        // so a non-absolute filename needs the directory ESLint itself was
+        // configured with. The node process cwd is only a fallback for harnesses
+        // that predate `getCwd`.
+        const cwd = typeof context.getCwd === 'function' ? context.getCwd() : process.cwd();
         const rawFilename = context.getFilename();
         const filename = rawFilename.replace(/\\/g, '/');
         const matchesTargetPath = targetPaths.some((pattern) => {
@@ -1089,7 +1101,7 @@ exports.requirePropsComposition = (0, createRule_1.createRule)({
             // the file reads, and it drops the dep from the *reported* set rather than
             // suppressing the whole report — a sibling child that genuinely needs
             // composition still fires.
-            const reportableDeps = depComponents.filter((dep) => !isPropLessImportedComponent(prog, dep, rawFilename, funcNode));
+            const reportableDeps = depComponents.filter((dep) => !isPropLessImportedComponent(prog, dep, rawFilename, funcNode, cwd));
             if (reportableDeps.length < minDependencyCount) {
                 return;
             }

package/lib/rules/test-file-location-enforcement.js

@@ -66,6 +66,13 @@ exports.testFileLocationEnforcement = (0, createRule_1.createRule)({
             ...SUPPORTED_EXTENSIONS,
             ...additionalExtensions.filter((extension) => !SUPPORTED_EXTENSIONS.includes(extension)),
         ];
+        // Anchor the reported path at the directory ESLint was configured with, not
+        // the node process cwd. The two differ under the VS Code ESLint extension,
+        // in monorepos, and for any programmatic `new ESLint({ cwd })`, where
+        // reading the process cwd names the misplaced test by a path the reader
+        // cannot locate (issue #1476). The `typeof` guard keeps the rule working
+        // under harnesses that predate `getCwd`.
+        const cwd = typeof context.getCwd === 'function' ? context.getCwd() : process.cwd();
         return {
             Program(node) {
                 const filename = context.getFilename();
@@ -84,7 +91,7 @@ exports.testFileLocationEnforcement = (0, createRule_1.createRule)({
                     return;
                 }
                 const relativePath = path_1.default.isAbsolute(filename)
-                    ? path_1.default.relative(process.cwd(), filename) || filename
+                    ? path_1.default.relative(cwd, filename) || filename
                     : filename;
                 // Naming the shortest prefix alongside the full stem keeps the guidance
                 // honest: either subject name satisfies the rule.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blumintinc/eslint-plugin-blumint",
-  "version": "1.20.39",
+  "version": "1.20.40",
   "description": "Custom eslint rules for use within BluMint",
   "author": {
     "name": "Brodie McGuire",

package/release-manifest.json

@@ -1,4 +1,46 @@
 [
+  {
+    "version": "1.20.40",
+    "date": "2026-07-30T23:29:30.176Z",
+    "rules": [
+      {
+        "name": "avoid-utils-directory",
+        "changeType": "fix",
+        "issues": [
+          1475
+        ],
+        "summary": "report the path relative to ESLint's cwd (closes #1475)"
+      },
+      {
+        "name": "enforce-assert-safe-object-key",
+        "changeType": "fix",
+        "issues": [
+          1473
+        ],
+        "summary": "anchor the injected import at ESLint's cwd (closes #1473)"
+      },
+      {
+        "name": "enforce-dynamic-imports",
+        "changeType": "fix",
+        "issues": [
+          1474
+        ],
+        "summary": "accept the helper modules this plugin's own fixers inject (closes #1474)"
+      },
+      {
+        "name": "require-props-composition",
+        "changeType": "fix",
+        "issues": [],
+        "summary": "resolve sibling components from ESLint's cwd"
+      },
+      {
+        "name": "test-file-location-enforcement",
+        "changeType": "fix",
+        "issues": [],
+        "summary": "name the file relative to ESLint's cwd"
+      }
+    ]
+  },
   {
     "version": "1.20.39",
     "date": "2026-07-30T21:18:09.189Z",