Upgrading request 1 to 2
Breaking1.9.9 → 2.88.2Breaking4Security4Platform2Deprecated1New109Changed49Fixed123Other312
BreakingUpgrade verdict
4 breaking changes and 2 platform requirement changes and 4 security fixes.
In plain terms
- Update eslintrc file to no longer allow past errors.
- Add back removed debug metadata.
- toJSON no longer results in an infinite loop, returns simple objects.
- Request.multipart no longer crashes when header 'Content-type' present.
Must act Top 5 of 11 that need code or config changes
Requires Node.js >= 6 from 2.88.2 (none stated before).
Adds aws-sign2 ~0.7.0, aws4 ^1.8.0, caseless ~0.12.0, combined-stream ~1.0.6, extend ~3.0.2, forever-agent ~0.6.1, form-data ~2.3.2, har-validator ~5.1.3, http-signature ~1.2.0, is-typedarray ~1.0.0, isstream ~0.1.2, json-stringify-safe ~5.0.1, mime-types ~2.1.19, oauth-sign ~0.9.0, performance-now ^2.1.0, qs ~6.5.2, safe-buffer ^5.1.2, tough-cookie ~2.5.0, tunnel-agent ^0.6.0, uuid ^3.3.2.
Installs 46 packages in all (was 0).
What you must change
Breaking4
Update eslintrc file to no longer allow past errors.
Add back removed debug metadata.
toJSON no longer results in an infinite loop, returns simple objects.
Request.multipart no longer crashes when header 'Content-type' present.
Security4
Updating tough-cookie due to security fix.
Security issue: Upgrade qs to version 6.4.0.
Remote Memory Exposure in request
Moderate · CVSS 5.9Fix security vulnerability.
Platform2
Drop support for Node 0.10.
Deprecate Node v0.8.x.
Deprecations to plan for
Deprecated1
Replace '.client' with '.socket' as the former was deprecated in 2.2.0.