Skip to content

Commit

Permalink
docs: improve wording of file-extension-in-import docs
Browse files Browse the repository at this point in the history
  • Loading branch information
cherryblossom000 authored Aug 21, 2023
1 parent 23ae475 commit b8b563d
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/rules/file-extension-in-import.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,9 @@ import foo from "./path/to/a/file" // maybe it's resolved to 'file.js' or 'file.
export * from "./path/to/a/file"
```

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

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.
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.

## 📖 Rule Details

Expand Down

0 comments on commit b8b563d

Please sign in to comment.