use eslint to enforce .js extensions with relative import paths #547
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
|
Holy shit, this is incredible |
|
Externalized to https://github.com/solana-labs/eslint-plugin-require-extensions. Thank you so much! |
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.
An eslint plugin which fixes #546
It should autofix code with
eslint --fixor on save with eslint plugins installed etcautofix.mov
You might want to give it a better name and publish it as an npm package if it's going to be shared amongst multiple repos, I put it in here as a starting point for convenience
I think it should cover all types of import and exports. I just pasted some code in https://astexplorer.net then copied the node type names