Update debug to 4.3.6 #162
Merged
Conversation
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
Member
|
Rebase and run npm install to re-lock, thanks! |
Member
I agree
Thanks for checking :) |
Signed-off-by: Matthew Peveler <[email protected]>
Contributor
Author
|
@eriktrom rebased |
Member
|
Gratzi! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
PR updates the library to use
debug:^4.3.6as dependency. This is the latest version (it's 2 behind), but I chose this version as it's the latest version that fixed JS deprecations or reported vulnerabilities, while still giving a bit of leeway to folks to dedupe if they already have a recentish version of debug installed.There are no direct tests for debug, so I tested it by doing
DEBUG=portfinder:* npm run testand confirming that the output remained the same between versions.