Add ESLint rule to require that relative imports use full extensions #279
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
SergeAstapov
force-pushed
the
lint-import-extensions
branch
3 times, most recently
from
905e48f to
4e73367
Compare
Use import ESLint plugin
SergeAstapov
force-pushed
the
lint-import-extensions
branch
2 times, most recently
from
2bc5010 to
bb65200
Compare
SergeAstapov
force-pushed
the
lint-import-extensions
branch
from
bb65200 to
b2dd794
Compare
|
thank you!!!! this is great! |
NullVoxPopuli
approved these changes
Mar 29, 2024
Merged
2 tasks
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.
Closes #220
Even though type-only imports are not supported (see import-js/eslint-plugin-import#2530), this already improves dx.