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
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.
Copy file name to clipboardexpand all lines: docs/rules/first.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ A directive in this case is assumed to be a single statement that contains only
45
45
a literal string-valued expression.
46
46
47
47
`'use strict'` would be a good example, except that [modules are always in strict
48
-
mode](http://www.ecma-international.org/ecma-262/6.0/#sec-strict-mode-code) so it would be surprising to see a `'use strict'` sharing a file with `import`s and
48
+
mode](https://262.ecma-international.org/6.0/#sec-strict-mode-code) so it would be surprising to see a `'use strict'` sharing a file with `import`s and
Copy file name to clipboardexpand all lines: docs/rules/no-duplicates.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@
3
3
Reports if a resolved path is imported more than once.
4
4
+(fixable) The `--fix` option on the [command line] automatically fixes some problems reported by this rule.
5
5
6
-
ESLint core has a similar rule ([`no-duplicate-imports`](http://eslint.org/docs/rules/no-duplicate-imports)), but this version
6
+
ESLint core has a similar rule ([`no-duplicate-imports`](https://eslint.org/docs/rules/no-duplicate-imports)), but this version
7
7
is different in two key ways:
8
8
9
9
1. the paths in the source code don't have to exactly match, they just have to point to the same module on the filesystem. (i.e. `./foo` and `./foo.js`)
0 commit comments