feat: swapping out the colors library for chalk #396
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.
🧰 Changes
This swaps out the colors library for chalk.
chalk
is a drop-in replacement forcolors
.Why?
chalk
has a lot more dev support thancolors
.colors
works by modifyingString.prototype
. Sure you can loadcolors/safe
to docolors.green()
but that's not the default flow.oas-normalize
and its dependency on@readme/openapi-parser
uses it by way of@readme/better-ajv-parser
so loading incolors
here for yet another way of colorizing CLI messaging is silly.text.green
and it only works because that command is loaded in./bin/rdme
whererequire('colors')
was present. Woof.🧬 QA & Testing