eslint-plugin-boundaries 2.9.0 → 2.10.2

package/README.md

@@ -163,7 +163,7 @@ Read the [docs of the `boundaries/entry-point` rule](docs/rules/entry-point.md)
 
 #### __`boundaries/element-types`__
 
-Define patterns to recognize each file in the project as one of this element types. All rules need this setting to be configured properly to work. The plugin tries to identify each file being analized or `import` statement in rules as one of the defined element types. The assigned element type will be that with the first matching pattern, in the same order that elements are defined in the array, so you __should sort them from the most accurate patterns to the less ones__. Properties of each `element`:
+Define patterns to recognize each file in the project as one of this element types. All rules need this setting to be configured properly to work. The plugin tries to identify each file being analyzed or `import` statement in rules as one of the defined element types. The assigned element type will be that with the first matching pattern, in the same order that elements are defined in the array, so you __should sort them from the most accurate patterns to the less ones__. Properties of each `element`:
 
 * __`type`__: `<string>` Element type to be assigned to files or imports matching the `pattern`. This type will be used afterwards in the rules configuration.
 * __`pattern`__: `<string>|<array>` [`micromatch` pattern](https://github.com/micromatch/micromatch). __By default the plugin will try to match this pattern progressively starting from the right side of each file path.__ This means that you don't have to define patterns matching from the base project path, but only the last part of the path that you want to be matched. This is made because the plugin supports elements being children of other elements, and otherwise it could wrongly recognize children elements as a part of the parent one. <br/>For example, given a path `src/helpers/awesome-helper/index.js`, it will try to assign the element to a pattern matching `index.js`, then `awesome-helper/index.js`, then `helpers/awesome-helper/index.js`, etc. Once a pattern matches, it assign the correspondent element type, and continues searching for parents elements with the same logic until the full path has been analyzed. __This behavior can be disabled setting the `mode` option to `full`__, then the provided pattern will try to match the full path.
@@ -298,7 +298,7 @@ Remember that:
 
 ##### Rules options properties
 
-* __`from/target`__: `<element matchers>` Depending of the rule to which the options are for, the rule will be applied only if the file being analized matches with this element matcher (`from`), or the dependency being imported matches with this element matcher (`target`).
+* __`from/target`__: `<element matchers>` Depending of the rule to which the options are for, the rule will be applied only if the file being analyzed matches with this element matcher (`from`), or the dependency being imported matches with this element matcher (`target`).
 * __`disallow/allow`__: `<value matchers>` If the plugin rule target matches with this, then the result of the rule will be "disallow/allow". Each rule will require a type of value here depending of what it is checking. In the case of the `element-types` rule, for example, another `<element matcher>` has to be provided in order to check the type of the local dependency.
 * __`message`__: `<string>` Optional. If the rule results in an error, the plugin will return this message instead of the default one. Read [error messages](#error-messages) for further info.
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "eslint-plugin-boundaries",
-  "version": "2.9.0",
+  "version": "2.10.2",
   "description": "Eslint plugin checking architecture boundaries between elements",
   "keywords": [
     "eslint",
@@ -31,22 +31,22 @@
     "eslint": ">=6.0.0"
   },
   "dependencies": {
-    "eslint-import-resolver-node": "0.3.6",
-    "eslint-module-utils": "2.7.3",
     "chalk": "4.1.2",
-    "is-core-module": "2.8.1",
-    "micromatch": "4.0.4"
+    "eslint-import-resolver-node": "0.3.6",
+    "eslint-module-utils": "2.7.4",
+    "is-core-module": "2.10.0",
+    "micromatch": "4.0.5"
   },
   "devDependencies": {
     "cross-env": "7.0.3",
-    "eslint": "8.9.0",
-    "eslint-config-prettier": "8.4.0",
-    "eslint-plugin-prettier": "4.0.0",
-    "husky": "7.0.4",
+    "eslint": "8.23.0",
+    "eslint-config-prettier": "8.5.0",
+    "eslint-plugin-prettier": "4.2.1",
+    "husky": "8.0.1",
     "is-ci": "3.0.1",
-    "jest": "27.5.1",
-    "lint-staged": "12.3.4",
-    "prettier": "2.5.1"
+    "jest": "29.0.1",
+    "lint-staged": "13.0.3",
+    "prettier": "2.7.1"
   },
   "lint-staged": {
     "test/**/*.js": "eslint",

package/resolver-legacy-alias/index.js

@@ -14,7 +14,7 @@ const replaceAliases = (filePath, config) => {
 
 module.exports = {
   interfaceVersion: 2,
-  resolve: function (source, file, config) {
+  resolve: function (source, _file, config) {
     if (resolve.isCore(source)) return { found: true, path: null };
     try {
       return {

package/src/rules/entry-point.js

@@ -14,7 +14,7 @@ function isMatchElementInternalPath(elementInfo, matcher, options) {
   return isMatchElementKey(elementInfo, matcher, options, "internalPath");
 }
 
-function elementRulesAllowEntryPoint(element, dependency, options) {
+function elementRulesAllowEntryPoint(_element, dependency, options) {
   return elementRulesAllowDependency({
     element: dependency,
     dependency,