@dword-design/eslint-plugin-import-alias 4.0.8 → 4.0.9

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 (2) hide show
  1. package/README.md +13 -1
  2. package/package.json +2 -2
package/README.md CHANGED
@@ -111,7 +111,19 @@ In this case lucky you, you don't have to do anything else. The plugin should wo
111
111
 
112
112
  If you have a special project setup that does not have a babel config in the project path, you can still use the plugin by passing the aliases directly to the rule. In this case you define the rule additionally in the `rules` section:
113
113
 
114
-
114
+ ```json
115
+ "rules": {
116
+ "@dword-design/import-alias/prefer-alias": [
117
+ "error",
118
+ {
119
+ "alias": {
120
+ "@": "./src",
121
+ "@components: "./src/components"
122
+ }
123
+ }
124
+ ]
125
+ }
126
+ ```
115
127
 
116
128
  <!-- LICENSE/ -->
117
129
  ## Contribute
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dword-design/eslint-plugin-import-alias",
3
- "version": "4.0.8",
3
+ "version": "4.0.9",
4
4
  "description": "An ESLint plugin that enforces the use of import aliases. Also supports autofixing.",
5
5
  "keywords": [
6
6
  "alias",
@@ -55,7 +55,7 @@
55
55
  "@dword-design/tester-plugin-tmp-dir": "^2.1.26",
56
56
  "depcheck-package-name": "^3.0.1",
57
57
  "eslint": "^8.0.0",
58
- "execa": "^7.1.1",
58
+ "execa": "^8.0.0",
59
59
  "fs-extra": "^11.1.1",
60
60
  "output-files": "^2.0.0"
61
61
  },