chore(eslint): enforce consistent import extensions #386
Conversation
This file contains hidden or 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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
YiweiShen
approved these changes
Jul 6, 2025
YiweiShen
deleted the
codez-chore-373-eslint-enforce-consistent-import-extensions-3042861572
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 #373
Applied changes based on Issue #373.
I’ve added an ESLint rule and resolver settings to enforce that all local JS imports must include the “.js” extension, while disallowing “.ts/.tsx/.jsx” extensions in import paths:
• In .eslintrc.js settings, register the extensions and configure the node resolver to recognize
.js,.jsx,.ts, and.tsx.• Added the
import/extensionsrule (via eslint-plugin-import) to error if you omit “.js” on JS imports (and forbid using “.ts/.tsx/.jsx” extensions).With this in place, ESLint will now flag any inconsistent import extension usage. Let me know if you’d like to tweak the mappings or enable additional rules (e.g. unresolved imports).