Add eslint import plugin to help detect unresolved paths #7416
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
Most of the rules in the import plugin are only useful for projects using purely ES6 imports. The `no-unresolved` rule works with mixed CommonJS and ES6 though, so we at least benefit from that in the meantime.
Certain lines only work after a build stage has been completed, so these failure can be ignored by the no-unresolved rule.
Gudahtt
force-pushed
the
add-eslint-import-plugin
branch
from
eddac08 to
9ca22d8
Compare
Builds ready [9ca22d8]
|
whymarrh
approved these changes
Nov 14, 2019
|
Gah, merged instead of squash. Oops. |
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.
Most of the rules in the import plugin are only useful for projects using purely ES6 imports. The
no-unresolvedrule works with mixed CommonJS and ES6 though, so we at least benefit from that in themeantime.