|
5 | 5 | [![coverage][codecov-image]][codecov-url] |
6 | 6 | [](https://ci.appveyor.com/project/import-js/eslint-plugin-import/branch/main) |
7 | 7 | [](https://www.npmjs.com/package/eslint-plugin-import) |
8 | | -[](http://www.npmtrends.com/eslint-plugin-import) |
| 8 | +[](https://www.npmtrends.com/eslint-plugin-import) |
9 | 9 |
|
10 | 10 | This plugin intends to support linting of ES2015+ (ES6+) import/export syntax, and prevent issues with misspelling of file paths and import names. All the goodness that the ES2015+ static module syntax intends to provide, marked up in your editor. |
11 | 11 |
|
@@ -256,7 +256,7 @@ the process's current working directory if no `package.json` is found. |
256 | 256 | If you are interesting in writing a resolver, see the [spec](./resolvers/README.md) for more details. |
257 | 257 |
|
258 | 258 | [`resolve`]: https://www.npmjs.com/package/resolve |
259 | | -[`externals`]: http://webpack.github.io/docs/library-and-externals.html |
| 259 | +[`externals`]: https://webpack.github.io/docs/library-and-externals.html |
260 | 260 |
|
261 | 261 | [Node]: https://www.npmjs.com/package/eslint-import-resolver-node |
262 | 262 | [webpack]: https://www.npmjs.com/package/eslint-import-resolver-webpack |
@@ -483,7 +483,7 @@ The purpose of the `chdir` setting, in this case, is to set the working director |
483 | 483 | from which ESLint is executed to be the same as the directory on which SublimeLinter-eslint |
484 | 484 | bases the relative path it provides. |
485 | 485 |
|
486 | | -See the SublimeLinter docs on [`chdir`](http://www.sublimelinter.com/en/latest/linter_settings.html#chdir) |
| 486 | +See the SublimeLinter docs on [`chdir`](https://www.sublimelinter.com/en/latest/linter_settings.html#chdir) |
487 | 487 | for more information, in case this does not work with your project. |
488 | 488 |
|
489 | 489 | If you are not using `.eslintignore`, or don't have a Sublime project file, you can also |
|
0 commit comments