Support --resolve-plugins-relative-to option
#279
Merged
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
|
Thank you for contributing! I have confirmed that |
mizdra
changed the title
--resolve-plugins-relative-to option
|
This feature is shipped in v10.7.0. |
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.
Summary
This Pull Request adds support for the
--resolve-plugins-relative-tooption in theeslint-interactiveBackground
In my monorepo project, I want to use the
eslint-interactivetool, but it requires support for the--resolve-plugins-relative-tooption which is available in ESLint.Tests
Although no new tests have been added, I have manually tested this change by building and executing
node /path/to/eslint-interactive/bin/eslint-interactive.js --resolve-plugins-relative-to=...command, and confirmed that it works correctly.