Make use of typescript import resolver #1509
Open
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
|
Hi! Is there anything I can do to help get this feature merged and a new version published? |
|
All efforts are currently towards flat config. You could apply for joining the work sessions. |
|
I couldn't find recent info on the sessions you mentioned. How do I apply? |
|
It should be renamed but here it is: |
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.
This pull request includes eslint-import-resolver-typescript as a peer dependency and enables TypeScript resolution for
eslint-plugin-import. And setsimport/no-unresolvedtoerrorDoing so we will also avoid having extraneous looking dependency in consumers package.json:
... "eslint-config-love": "46.0.0", "eslint-import-resolver-typescript": "3.6.1", ...