Update checked-in dependencies
This commit is contained in:
parent
a0ab4842b5
commit
068ade0b31
93 changed files with 4472 additions and 4635 deletions
10
node_modules/eslint-plugin-import/README.md
generated
vendored
10
node_modules/eslint-plugin-import/README.md
generated
vendored
|
|
@ -1,8 +1,8 @@
|
|||
# eslint-plugin-import
|
||||
|
||||
[](https://travis-ci.org/benmosher/eslint-plugin-import)
|
||||
[](https://coveralls.io/github/benmosher/eslint-plugin-import?branch=master)
|
||||
[](https://ci.appveyor.com/project/benmosher/eslint-plugin-import/branch/master)
|
||||
[](https://travis-ci.org/import-js/eslint-plugin-import)
|
||||
[](https://coveralls.io/github/import-js/eslint-plugin-import?branch=master)
|
||||
[](https://ci.appveyor.com/project/import-js/eslint-plugin-import/branch/master)
|
||||
[](https://www.npmjs.com/package/eslint-plugin-import)
|
||||
[](http://www.npmtrends.com/eslint-plugin-import)
|
||||
|
||||
|
|
@ -190,7 +190,7 @@ runtime (allowing some modules to be included more traditionally via script tags
|
|||
In the interest of supporting both of these, v0.11 introduces resolvers.
|
||||
|
||||
Currently [Node] and [webpack] resolution have been implemented, but the
|
||||
resolvers are just npm packages, so [third party packages are supported](https://github.com/benmosher/eslint-plugin-import/wiki/Resolvers) (and encouraged!).
|
||||
resolvers are just npm packages, so [third party packages are supported](https://github.com/import-js/eslint-plugin-import/wiki/Resolvers) (and encouraged!).
|
||||
|
||||
You can reference resolvers in several ways (in order of precedence):
|
||||
|
||||
|
|
@ -348,6 +348,8 @@ An array of folders. Resolved modules only from those folders will be considered
|
|||
|
||||
This option is also useful in a monorepo setup: list here all directories that contain monorepo's packages and they will be treated as external ones no matter which resolver is used.
|
||||
|
||||
If you are using `yarn` PnP as your package manager, add the `.yarn` folder and all your installed dependencies will be considered as `external`, instead of `internal`.
|
||||
|
||||
Each item in this array is either a folder's name, its subpath, or its absolute prefix path:
|
||||
|
||||
- `jspm_modules` will match any file or folder named `jspm_modules` or which has a direct or non-direct parent named `jspm_modules`, e.g. `/home/me/project/jspm_modules` or `/home/me/project/jspm_modules/some-pkg/index.js`.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue