BREAKING CHANGE: Always require file extension for imports #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
titouanmathis
force-pushed
the
feature/always-require-file-extension
branch
from
583c88c to
23dd94b
Compare
KeziahMoselle
approved these changes
Apr 12, 2021
|
👍 |
Merged
titouanmathis
added a commit
that referenced
this pull request
Jan 4, 2022
v3.0.0-beta.0 Added - Add best practices rules from [eslint-plugin-unicorn](https://github.com/sindresorhus/eslint-plugin-unicorn) (#33) - Add JS Doc rules from [eslint-plugin-jsdoc](https://github.com/gajus/eslint-plugin-jsdoc) (#33) - Add [@rushstack/eslint-patch](https://github.com/microsoft/rushstack/blob/master/eslint/eslint-patch/README.md) to fix plugin issues (#33) Changed - **Breaking:** Always require file extension for imports (#22)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As the JS ecosystem grows towards modules, using file extensions for imports is becoming the norm (see Node.js modules and vitejs/vite#178 (comment) for Vue).
This PR updates the ESLint rule
import/extensionto always require file extension.This is a breaking change.