@blumintinc/eslint-plugin-blumint 1.20.200 → 1.20.201

package/lib/index.js

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

package/lib/rules/use-custom-link.js

@@ -71,23 +71,27 @@ exports.useCustomLink = (0, createRule_1.createRule)({
                     const defaultAsSpecifier = importSpecifiers.find((specifier) => specifier.type === 'ImportSpecifier' &&
                         specifier.imported.name === 'default');
                     if (defaultSpecifier || defaultAsSpecifier) {
+                        // The fix rebuilds the whole declaration from the default binding
+                        // alone, so any other specifier would be deleted outright and
+                        // whatever still references it left dangling — including an
+                        // `export { LinkProps }` that keeps the exported NAME while losing
+                        // what it resolves to. Relocating them instead is not available:
+                        // whether the wrapper re-exports a given specifier is unknowable
+                        // from here, so carrying them over would trade a silent dangling
+                        // binding for a possibly unresolvable import. Decline the fix and
+                        // keep the report, so the migration stays a deliberate edit.
+                        const droppedSpecifiers = importSpecifiers.filter((specifier) => specifier !== defaultSpecifier &&
+                            specifier !== defaultAsSpecifier);
+                        const localName = defaultSpecifier?.local?.name ||
+                            defaultAsSpecifier?.local?.name ||
+                            'Link';
                         context.report({
                             node,
                             messageId: 'useCustomLink',
-                            data: {
-                                localName: defaultSpecifier?.local?.name ||
-                                    defaultAsSpecifier?.local?.name ||
-                                    'Link',
-                            },
-                            fix(fixer) {
-                                // Get the local name of the imported Link component
-                                const localName = defaultSpecifier?.local?.name ||
-                                    defaultAsSpecifier?.local?.name ||
-                                    'Link';
-                                // Create the new import statement
-                                const newImport = `import ${localName} from '${LINK_MODULE_PATH}';`;
-                                return fixer.replaceText(node, newImport);
-                            },
+                            data: { localName },
+                            fix: droppedSpecifiers.length > 0
+                                ? undefined
+                                : (fixer) => fixer.replaceText(node, `import ${localName} from '${LINK_MODULE_PATH}';`),
                         });
                     }
                 }

package/lib/utils/harvestRuleTesterCases.d.ts

@@ -49,7 +49,7 @@ export type HarvestResult = {
  * Only suites that import the shared tester module can declare a case, since
  * `src/tests/no-local-rule-tester.test.ts` forbids a locally-built tester. That
  * makes the import a sound admission test rather than a heuristic, and it is
- * what keeps this affordable: the ~28 files it excludes are the meta-suites
+ * what keeps this affordable: the files it excludes are the meta-suites
  * (`fixer-type-safety`, `docs-examples-conformance`, `rule-crash-robustness`,
  * this guard's own siblings) which run full corpus sweeps at module scope and
  * cost more to load than every rule suite combined.

package/lib/utils/harvestRuleTesterCases.js

@@ -33,7 +33,7 @@ const TESTS_DIR = path.join(__dirname, '..', 'tests');
  * Only suites that import the shared tester module can declare a case, since
  * `src/tests/no-local-rule-tester.test.ts` forbids a locally-built tester. That
  * makes the import a sound admission test rather than a heuristic, and it is
- * what keeps this affordable: the ~28 files it excludes are the meta-suites
+ * what keeps this affordable: the files it excludes are the meta-suites
  * (`fixer-type-safety`, `docs-examples-conformance`, `rule-crash-robustness`,
  * this guard's own siblings) which run full corpus sweeps at module scope and
  * cost more to load than every rule suite combined.

package/package.json

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

package/release-manifest.json

@@ -1,4 +1,18 @@
 [
+  {
+    "version": "1.20.201",
+    "date": "2026-09-01T19:58:16.746Z",
+    "rules": [
+      {
+        "name": "use-custom-link",
+        "changeType": "fix",
+        "issues": [
+          2272
+        ],
+        "summary": "decline the autofix when it would drop a specifier (closes #2272)"
+      }
+    ]
+  },
   {
     "version": "1.20.200",
     "date": "2026-09-01T14:50:44.328Z",