-
Notifications
You must be signed in to change notification settings - Fork 168
Open
Description
After updating to v8 we now have a new set of dependencies because of request postman:
postman-request@^2.88.1-postman.30:
version "2.88.1-postman.30"
resolved "https://registry.yarnpkg.com/postman-request/-/postman-request-2.88.1-postman.30.tgz#44554fd3c19bf19e0a583e92b654d3c4f7e4669e"
integrity sha512-zsGvs8OgNeno1Q44zTgGP2IL7kCqUy4DAtl8/ms0AQpqkIoysrxzR/Zg4kM1Kz8/duBvwxt8NN717wB7SMNm6w==
dependencies:
"@postman/form-data" "~3.1.1"
"@postman/tunnel-agent" "^0.6.3"
aws-sign2 "~0.7.0"
aws4 "^1.8.0"
brotli "~1.3.2"
caseless "~0.12.0"
combined-stream "~1.0.6"
extend "~3.0.2"
forever-agent "~0.6.1"
har-validator "~5.1.3"
http-signature "~1.3.1"
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"
stream-length "^1.0.2"
tough-cookie "~2.5.0"
uuid "^3.3.2"
Not only it makes downloading node modules slower but it's also a higher audit maintenance cost. Is this really necessary just to make a few API calls to a well known API? Can't you use node-fetch
or even the native http library?
A general purpose HTTP library to make requests to a known and sanitised API seems a bit too excessive.
Metadata
Metadata
Assignees
Labels
No labels