Use path.join() when specifying output directory#178
Merged
Conversation
|
|
evenstensberg
self-requested a review
August 14, 2017 15:14
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
What kind of change does this PR introduce?
Always use
path.resolve()when writing theoutput.path.Did you add tests for your changes?
Nope.
If relevant, did you update the documentation?
Nope.
Summary
Previously, using the default value of "dist" would correctly use
path.resolve()when specifying an output path, whereas specifying a custom path would use that path directly withoutpath.resolve(). This PR should make it more consistent. 🤞Does this PR introduce a breaking change?
Nope.
Other information
Fixes #177