Great package but can have destructive results on your package.json about yarn-upgrade-all HOT 2 CLOSED

I am not sure I am going to do that.

First of all, as you said, most projects have version control, you can git stash to revert the breaking change.

Secondly, to me, control c and cryptic error in node are “force majeure”. This package (and most other utility packages) is not responsible for that.

Lastly, even you restore/merge the temp package.json file there are still issues: node_modules/ is not in a ready state because package missing or version mis-matching with package.json.

from yarn-upgrade-all.

Another case is when there is a bad network connection or package compatibility issue, a package cannot be installed.

In such cases the recommended solution is to install that package manually. Because in such case there is unlikely a reliable and automatic way to fix the issue. You'd have to fix the issue manually whatever.

from yarn-upgrade-all.