fix available via `npm audit fix --force`
^ will actually downgrade packages
wtf

Older versions are better

You did tell it to fix the problem, you didn't really tell it how though beyond " I don't care what you do, just fix it"

It's not wrong to downgrade a package in package management.

But... And that's a huge but. I still don't think that Node is a *good* package management system.

It's more clusterfuck squared....

E.g. this force parameter... I've attached a picture from the NPM node docs.

No sane package system should ever do that... Allowing to override certain behaviour or to deliberately say yes to confirmation even if it's dangerous. Okay...

But not - in a nutshell - just throw every configuration over board and turn to "I'll just try to solve this gunshot style" is really ... Dumb.