fix: ensure supportsColor.level exists before stringifying it #901
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.
When supports-color detects a level of 0, it will not return an object containing the key
level
, but instead onlyfalse
. This commit makes suresupportsColor.level
exists before callingsupportsColor.level.toString()
.The TypeScript definitions of
chalk
seem wrong in this regard, since they imply that ifsupportsColor
is truthy, it is an object and always contains thelevel
key of type0 | 1 | 2 | 3
.