Open t-fine opened 2 years ago
@t-fine so I see two somewhat conflicting bits of work here. One is to just make sure we don't have security vulnerabilities in our code, and the other is to update cloud/sdr
as a whole so we can verify that the security fixes we're introducing aren't breaking the code. Given that the security updates have taken priority in the past, I'm going to spin off a new issue to get cloud/sdr
working again independently of the security updates. Then, we don't have to care about those manual fixes as much until we're at a place where cloud/sdr
is working again.
Look up "latest" npm
version and go from there
There are currently 17 moderate and high severity security vulnerabilities related to the sdr cloud app code. It has gotten to a point
npm update
can not resolve the dependency tree automatically and will need some more involved and manual fixes as some of the updates will likely involve breaking changes.