Skip to content

docs: improve wording of file-extension-in-import docs #110

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Feb 22, 2024
Merged

docs: improve wording of file-extension-in-import docs #110

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
977825d
docs: improve wording of file-extension-in-import docs
cherryblossom000 Aug 21, 2023
d367a06
Update docs/rules/file-extension-in-import.md
scagood Feb 22, 2024
3bbee59
docs: Remove multiple blank lines
scagood Feb 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 1 addition & 3 deletions docs/rules/file-extension-in-import.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,7 @@ 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.

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