-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update superagent dependency #121
Comments
Hi @mhoffmann-attempto |
I am getting "Refused to set unsafe header "user-agent"" as console error, is this issue related? |
Hi @shubhamUpadhyayInBlue – I am getting warnings for three packages that you are pulling in: node_modules/querystring: node_modules/superagent: node_modules/superagent/node_modules/formidable: All packages are dependencies of > npm explain querystring
[email protected]
node_modules/querystring
querystring@"0.2.0" from [email protected]
node_modules/sib-api-v3-sdk
sib-api-v3-sdk@"^8.4.0" from the root project
> npm explain superagent
[email protected]
node_modules/superagent
superagent@"3.7.0" from [email protected]
node_modules/sib-api-v3-sdk
sib-api-v3-sdk@"^8.4.0" from the root project
> npm explain formidable
[email protected]
node_modules/formidable
formidable@"^2.0.1" from the root project
[email protected]
node_modules/superagent/node_modules/formidable
formidable@"^1.1.1" from [email protected]
node_modules/superagent
superagent@"3.7.0" from [email protected]
node_modules/sib-api-v3-sdk
sib-api-v3-sdk@"^8.4.0" from the root project |
I'm having the same warnings. Since formidable is a dependency of the superagent package, I've been able to fix both formidable and superagent by adding an override to my package.json like so:
I'm still working on the [email protected] warning. |
Actually, for some reason in my most recent commits, I'm no longer getting the deprecation warning for [email protected], even though I haven't successfully troubleshooted it. I'm not sure if I should still be concerned... but I'll go with it for now since I still have all the functionality I should be getting. |
Thanks @TheLionIsAlive , yes overriding the version is a workaround for now. But, I checked if I have to upgrade to this version in the SDK it does not support Node v10. So, it will be a breaking change that I will have to release. I will do it after new development changes are live in a minor release first. Thanks! |
I look forward to it! Thanks for the reply.
…On Mon, Jan 16, 2023, 04:39 shubhamUpadhyayInBlue ***@***.***> wrote:
Thanks @TheLionIsAlive <https://github.com/TheLionIsAlive> , yes
overriding the version is a workaround for now. But, I checked if I have to
upgrade to this version in the SDK it does not support Node v10. So, it
will be a breaking change that I will have to release. I will do it after
new development changes are live in a minor release first.
Thanks!
—
Reply to this email directly, view it on GitHub
<#121 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AXKJH6ZRWQ4GGJKK4NYHTMTWSUQODANCNFSM5VHWELQQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
As I see you use superagent in version 3.7.0. (5 jears old)
It has a vulnerability: OSS Vulnerability
Is it possible to update the version to a more actual one? (e.g. 7.x ?)
see: npm superagent
The text was updated successfully, but these errors were encountered: