Skip to content

Commit b8b563d

Browse files
docs: improve wording of file-extension-in-import docs
mysticatea#325
1 parent 23ae475 commit b8b563d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/rules/file-extension-in-import.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,9 +11,9 @@ import foo from "./path/to/a/file" // maybe it's resolved to 'file.js' or 'file.
1111
export * from "./path/to/a/file"
1212
```
1313

14-
However, [--experimental-modules](https://medium.com/@nodejs/announcing-a-new-experimental-modules-1be8d2d6c2ff) has declared to drop the file extension omition.
14+
However, when using [`--experimental-modules`](https://medium.com/@nodejs/announcing-a-new-experimental-modules-1be8d2d6c2ff), file extensions are required.
1515

16-
Also, we can import a variety kind of files with bundlers such as Webpack. In the situation, probably explicit file extensions help us to understand code.
16+
We can also import a variety of file types with bundlers such as Webpack. In this situation, explicit file extensions can help to identify the type of file being imported.
1717

1818
## 📖 Rule Details
1919

0 commit comments

Comments
 (0)