fix: don't use path.extname with undefined value #5683
Merged
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.
In the current versions of node path.* can be called on any arbitrary
value and will return an empty string on invalid input.
As of node v6 path will assert that values passed to it are strings,
and as such will throw on
undefined
This commit moved the logic of using
path.extname
inside of theprocessText function in
lib/cli-engine.js
. so that it will not callpath.extname
if a filename is not passed.This change should not affect any other parts of the system, and the
test suite is 100% working on node v4, v5, and master.
fixes #5678