Load local jake module if it exists #331
Closed
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
|
@navneetgarg123 I know this is quite the old PR, but with the current load order of Node these days do you know if this is still necessary? I did a quick test and it doesn't seem like it is. Thanks! |
|
I think I already rewrote this so that it looks for local Jake, but falls back to global if it can't find one. |
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.
Currently, the global
jakeexecutable will always load the globally installed module. This PR allows for a local installation ofjaketo be required if it exists instead. This is necessary with a project that requires a locally installedjakeand is run with a globally installedjake.