eslint-plugin-use-agnostic 1.7.1 → 1.7.3

package/jscomments/_commons/constants/data.js

@@ -4,3 +4,5 @@ import { resolvedConfigData } from "../../../comments.config.mjs";
 
 /** @type {ResolvedConfigData} `resolvedConfigData` can be imported as is but I've noticed that for some reason the type-safety is more advanced when it is re-typed and re-exported, here as `commentVariablesData`. */
 export const commentVariablesData = resolvedConfigData;
+
+export const directive21Data = commentVariablesData.directive21;

package/library/index.js

@@ -130,3 +130,5 @@ export {
   getStrategizedDirective,
   isImportBlocked as isImportBlockedDirective21,
 } from "./directive21/_commons/utilities/helpers.js";
+
+export { directive21Data } from "../jscomments/_commons/constants/data.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eslint-plugin-use-agnostic",
-  "version": "1.7.1",
+  "version": "1.7.3",
   "description": "Highlights problematic server-client imports in projects made with the Fullstack React Architecture.",
   "keywords": [
     "eslint",

package/types/index.d.ts

@@ -16,8 +16,6 @@ export const directive21ConfigName: "directive21";
 export const enforceEffectiveDirectivesRuleName: "enforce-effective-directives-import-rules";
 export const enforceCommentedDirectivesRuleName: "enforce-commented-directives-import-rules";
 
-// NEW
-
 // JavaScript/TypeScript extensions array
 export const EXTENSIONS: readonly [
   ".tsx",
@@ -328,6 +326,9 @@ export const commentedDirectives_reactDirectives: Readonly<{
   [USE_AGNOSTIC_STRATEGIES]: null;
 }>;
 
+/** Typing currently unavailable. To be used by chaining `.importingCommentedDirective` `.importedCommentedDirective` `.value` to obtain the reason why a module import is or isn't allowed. */
+export const directive21Data: object;
+
 /**
  * Gets the commented directive of a module from its ESLint `SourceCode` object.
  *