issue #661: Refine a path resolution for node tasks #662
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
- an executable (such as gulp) is found regardless of extension used (supported by node, i.e. no extension, js, json, and node) - revamp log messages - reuse paths-related utils
|
@eirslett bumping |
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
Tests and Documentation
I've tested the change locally in a few scenarios with different correct/invalid task paths.
I can see
gulphappy path is already covered init/example project. I'm wondering why it didn't fail for1.6release... Should I add new directory initespecially for this change?IMO docs change it's not needed here, because it's about internal behaviour, but I might be wrong.