Update debug package to version 4.0.0
See original GitHub issueI am getting warnings in my CI due to updated debug package:
warning axios > follow-redirects > debug@3.2.4: `debug` versions 3.2.0-3.2.2 break Node 4. Users of node LTS and onward (modern Node versions): please upgrade to `debug@4` or above as soon as possible. Node 4 users: please pin to `debug@>=3.2.3 <4` as it will be the last version range that supports Node@4.
The debug
project recommends a package update to version 4.0.0 to mitigate vulnerabilities and performance improvement.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Update debug package to version 4.0.0 · Issue #8674 - GitHub
Bug Report Current Behavior I am getting warnings in my CI due to updated debug package: debug-js/debug#603 (comment) ...
Read more >System.Diagnostics.Debug 4.0.0 - NuGet
Provides classes and attributes that allows basic interaction with a debugger. Commonly Used Types: System.Diagnostics.Debug System.
Read more >@boost/debug - npm
Lightweight debugging and crash reporting.. Latest version: 4.0.0, last published: 3 months ago. Start using @boost/debug in your project by ...
Read more >"Debug location is approximate because the source is not ...
Reinstalling the package from GitHub using devtools::install_github(); Checked package root; Updated all dependency packages; Repeated the ...
Read more >update-package-versions-status — AWS CLI 1.27.40 ...
The following update-package-versions-status example updates the status of version 4.0.0 of the test-package package to Archived. aws codeartifact update- ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
On second thought, I think your next CI build should be alright actually. You probably only saw errors because faulty versions were temporarily online. New installs should now use 3.2.4, which is fine with Node 4. Nonetheless, I’m pinning to 3.1.0 just in case, and will use 4.x once we drop Node 4.
Mmm bad decision on their part. Fixed then.