Security update (v2.0.4)
i have updated one library for security update.
Naturally ... I have updated the library (because new library have new part of code) and there is some brake change in the main code of MMM-Tools and I apply it.
you should have no 0 vulnerabilities at now
Force upgrading an library by a final use (by you) is not a good solution (
npm audit fixfor exemple)
A new library have some change or break change !
So, You can have some error or no result query.
Break changeis change dial with library or response displaying (or response deleted and/or replaced by another function)
That why ONLY developer can apply this operation.
the developer will apply upgrade with package.json and apply any modifications of the module code.
Of Course, it related to ALL modules that you use (not only my modules)