[Snyk(Unlimited)] Upgrade debug from 2.0.0 to 4.1.1 #1626
Conversation
This file contains 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
Snyk has created this PR to upgrade debug from 2.0.0 to 4.1.1. See this package in NPM: https://www.npmjs.com/package/debug See this project in Snyk: https://app.snyk.io/org/auto-upgrade-pr/project/085294bc-595f-40ee-a928-3fde17d29fe6?utm_source=github&utm_medium=upgrade-pr
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Snyk has created this PR to upgrade
debugfrom 2.0.0 to 4.1.1.Warning: This is a major version upgrade, and may be a breaking change.
The recommended version fixes:
Release notes
This backport fixes a bug in coveralls configuration as well as the
.extend()function.Patches
Minor Changes
Massive thank you to @mblarsen and @outsideris for knocking out two long-awaited changes.
This patch restores browserify functionality as well as keeping the intended functionality with Unpkg.com.
Patches
A long-awaited release to
debugis available now:4.0.0.Due to the delay in release and the number of changes made (including bumping dependencies in order to mitigate vulnerabilities), it is highly recommended maintainers update to the latest package version and test thoroughly.
This release drops support for Node 4 and 5 in alignment with the Node.js LTS Release Schedule.
Major Changes
Minor Changes
Patches
chrome.storage(or make the storage backend pluggable): 71d2aa7supports-color@5: 285dfe1enable()(#517): ab5083fCredits
Huge thanks to @DanielRuf, @EirikBirkeland, @KyleStay, @Qix-, @abenhamdine, @alexey-pelykh, @DiegoRBaquero, @febbraro, @kwolfy, and @TooTallNate for their help!
This backport fixes a 4x performance regression when debug is disabled.
Patches
This patch restores browserify functionality as well as keeping the intended functionality with Unpkg.com.
It is a backport of the
4.0.1release.Patches
This released fixed the missing
filesentry inpackage.json, mitigating the faulty3.2.3release.This release mitigated the breaking changes introduced in
3.2.0where./node.jswas removed, breaking a very select few users on older releases ofbabel-core, as well as users that used an undocumentedrequire('debug/node')../node.jswas temporarily added to the repository at this time; however, this release failed to includenode.jsin thefileskey inpackage.jsonand thus didn't fix the issue.3.2.4rectified this issue.This release mitigated the breaking changes introduced in
3.2.0where ES6 features were being used on users of Node 4, causing crashes upon inclusion.It employed a temporary Babel pass on the entire codebase in lieu of a hard reversion (so this version is, effectively, a backport of the fixes and features ultimately introduced in
4.0.0).This release, along with
3.2.0, were subsequently released together as4.0.0(a major bump). You can review the complete changes in that release's details.A quick hotfix to address Browser builds -
debugis now compiled down to IE8-compatible code via Babel upon release.CDNs that honor the
"browser":key inpackage.jsonshould now reflect these changes (previously, they would serve the non-bundled ES6 version).Patches
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs