use the local linter version when possible #101
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
|
Nice @devtristan 👍, great job on this. I'll review as soon as possible as this solves a bunch of issues. |
|
Great job 👍 |
This was referenced Apr 11, 2016
Closed
|
Thanks for this! Sweet fix 👍 :) |
|
So glad I could help. |
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.
Solves #65 #89 #86 #76 #72
Uses the linter your package depends on rather than the internal dependency whenever possible. This means that when you update standard in your package.json devDependencies, linter-js-standard will use that version. Also means that this package doesn't need to be updated constantly whenever a new version of anything comes out.