npm - @alextheman/eslint-plugin - Versions diffs - 2.7.2 → 2.7.3 - Mend

@alextheman/eslint-plugin 2.7.2 → 2.7.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.

Files changed (5) hide show

package/dist/index.cjs CHANGED Viewed

@@ -3758,7 +3758,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var name = "@alextheman/eslint-plugin";
-var version = "2.7.2";
+var version = "2.7.3";
 // src/configs/index.ts
 var import_eslint_plugin_package_json = __toESM(require("eslint-plugin-package-json"), 1);
@@ -4129,19 +4129,46 @@ var typeScriptBase = [
 var typeScriptBase_default = typeScriptBase;
 // src/configs/personal/eslintPlugin.ts
+var import_eslint_plugin_perfectionist2 = __toESM(require("eslint-plugin-perfectionist"), 1);
 function createPersonalEslintPluginConfig(plugin) {
+  const noPluginImportMessage = "Do not import the plugin directly from the config files. Please create a function that takes in the plugin and returns the config instead.";
   return [
     {
       plugins: {
-        "@alextheman": plugin
+        "@alextheman": plugin,
+        perfectionist: import_eslint_plugin_perfectionist2.default
       },
       rules: {
-        // When we pass the plugin into the config creator functions from the index, there's no guarantee that the configs will already be
-        // on the plugin when you access them from src/configs, since they're in the process of being created. It is generally better to import
-        // another creator function directly from the creator function should you need to refer to another config in the newly added config. */
         "@alextheman/no-plugin-configs-access-from-src-configs": "error"
       }
     },
+    {
+      files: ["src/configs/**"],
+      rules: {
+        "no-restricted-imports": [
+          "error",
+          {
+            paths: [
+              {
+                importNames: ["default"],
+                message: noPluginImportMessage,
+                name: "src/alexPlugin"
+              },
+              {
+                importNames: ["default"],
+                message: noPluginImportMessage,
+                name: "src/index"
+              },
+              {
+                importNames: ["default"],
+                message: noPluginImportMessage,
+                name: "src"
+              }
+            ]
+          }
+        ]
+      }
+    },
     {
       // Since the object exported in the rules index serves the same function as the exports in other projects, it's best to sort them in alphabetical order
       // as well to make it easier to compare against the file directory.

package/dist/index.d.cts CHANGED Viewed

@@ -4,7 +4,7 @@ import { Config } from 'prettier';
 import z from 'zod';
 var name = "@alextheman/eslint-plugin";
-var version = "2.7.2";
+var version = "2.7.3";
 type CamelToKebab<S extends string> = S extends `${IgnoreCase<"J">}avaScript${infer Rest}` ? Rest extends "" ? "javascript" : `javascript${CamelToKebab<Rest>}` : S extends `${IgnoreCase<"T">}ypeScript${infer Rest}` ? Rest extends "" ? "typescript" : `typescript${CamelToKebab<Rest>}` : S extends `${infer Head}${infer Tail}` ? Head extends Lowercase<Head> ? `${Head}${CamelToKebab<Tail>}` : `-${Lowercase<Head>}${CamelToKebab<Tail>}` : S;

package/dist/index.d.ts CHANGED Viewed

@@ -4,7 +4,7 @@ import { Config } from 'prettier';
 import z from 'zod';
 var name = "@alextheman/eslint-plugin";
-var version = "2.7.2";
+var version = "2.7.3";
 type CamelToKebab<S extends string> = S extends `${IgnoreCase<"J">}avaScript${infer Rest}` ? Rest extends "" ? "javascript" : `javascript${CamelToKebab<Rest>}` : S extends `${IgnoreCase<"T">}ypeScript${infer Rest}` ? Rest extends "" ? "typescript" : `typescript${CamelToKebab<Rest>}` : S extends `${infer Head}${infer Tail}` ? Head extends Lowercase<Head> ? `${Head}${CamelToKebab<Tail>}` : `-${Lowercase<Head>}${CamelToKebab<Tail>}` : S;

package/dist/index.js CHANGED Viewed

@@ -3743,7 +3743,7 @@ var require_src = __commonJS({
 // package.json
 var name = "@alextheman/eslint-plugin";
-var version = "2.7.2";
+var version = "2.7.3";
 // src/configs/index.ts
 import packageJson from "eslint-plugin-package-json";
@@ -4114,19 +4114,46 @@ var typeScriptBase = [
 var typeScriptBase_default = typeScriptBase;
 // src/configs/personal/eslintPlugin.ts
+import perfectionist2 from "eslint-plugin-perfectionist";
 function createPersonalEslintPluginConfig(plugin) {
+  const noPluginImportMessage = "Do not import the plugin directly from the config files. Please create a function that takes in the plugin and returns the config instead.";
   return [
     {
       plugins: {
-        "@alextheman": plugin
+        "@alextheman": plugin,
+        perfectionist: perfectionist2
       },
       rules: {
-        // When we pass the plugin into the config creator functions from the index, there's no guarantee that the configs will already be
-        // on the plugin when you access them from src/configs, since they're in the process of being created. It is generally better to import
-        // another creator function directly from the creator function should you need to refer to another config in the newly added config. */
         "@alextheman/no-plugin-configs-access-from-src-configs": "error"
       }
     },
+    {
+      files: ["src/configs/**"],
+      rules: {
+        "no-restricted-imports": [
+          "error",
+          {
+            paths: [
+              {
+                importNames: ["default"],
+                message: noPluginImportMessage,
+                name: "src/alexPlugin"
+              },
+              {
+                importNames: ["default"],
+                message: noPluginImportMessage,
+                name: "src/index"
+              },
+              {
+                importNames: ["default"],
+                message: noPluginImportMessage,
+                name: "src"
+              }
+            ]
+          }
+        ]
+      }
+    },
     {
       // Since the object exported in the rules index serves the same function as the exports in other projects, it's best to sort them in alphabetical order
       // as well to make it easier to compare against the file directory.

package/package.json CHANGED Viewed

@@ -1,6 +1,6 @@
 {
   "name": "@alextheman/eslint-plugin",
-  "version": "2.7.2",
+  "version": "2.7.3",
   "description": "A package to provide custom ESLint rules and configs",
   "license": "ISC",
   "author": "alextheman",
@@ -11,7 +11,7 @@
     "dist"
   ],
   "scripts": {
-    "build": "tsup",
+    "build": "tsup && npx tsx src/utility/hashConfigChanges.ts",
     "change-major": "npm version major -m \"Change version number to v%s\"",
     "change-minor": "npm version minor -m \"Change version number to v%s\"",
     "change-patch": "npm version patch -m \"Change version number to v%s\"",