Update packages with security vulnerabilities

[garg3133]

If you set up this project locally (fork, clone and then run npm i) and do npm audit, you'll see that a lot of packages that this project is dependent on have security vulnerabilities in them.

So, we'd need to update the packages iteratively to handle these security vulnerabilities while also making sure that upgrading to newer versions don't end up breaking the tool in some way or another.

[AkhilJ321]

@garg3133, for low severity fixes which will not break the code can be done by npm audit fix , then for the remaining do we need to do them manually and check for compatibility, or implement some kind of script or automated testing?

[garg3133]

I'd suggest doing them manually to ensure compatibility. But you can work on these iteratively, first fix the easier ones and open a PR and then iterate over the more severe ones and open a PR as you go from one consistent state to another.

[AkhilJ321]

@garg3133 ,can you review the PR and check if I am going in the right direction?