You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -145,7 +145,7 @@ In the interest of supporting both of these, v0.11 introduces resolvers.
145
145
Currently [Node] and [Webpack] resolution have been implemented, but the
146
146
resolvers are just npm packages, so [third party packages are supported](https://github.com/benmosher/eslint-plugin-import/wiki/Resolvers) (and encouraged!).
147
147
148
-
You can reference resolvers in several ways(in order of precedence):
148
+
You can reference resolvers in several ways(in order of precedence):
149
149
150
150
- as a conventional `eslint-import-resolver` name, like `eslint-import-resolver-foo`:
Copy file name to clipboardExpand all lines: docs/rules/no-unassigned-import.md
+22
Original file line number
Diff line number
Diff line change
@@ -6,11 +6,24 @@ With both CommonJS' `require` and the ES6 modules' `import` syntax, it is possib
6
6
7
7
This rule aims to remove modules with side-effects by reporting when a module is imported but not assigned.
8
8
9
+
### Options
10
+
11
+
This rule supports the following option:
12
+
13
+
`allow`: An Array of globs. The files that match any of these patterns would be ignored/allowed by the linter. This can be useful for some build environments (e.g. css-loader in webpack).
14
+
15
+
Note that the globs start from the where the linter is executed (usually project root), but not from each file that includes the source. Learn more in both the pass and fail examples below.
0 commit comments