vscode-eslint: Could ESLint extension be more vocal about rule syntax problems?

Having spent loads of time on a setup where I wouldn’t need Prettier in the mix, and where only eslint fixers do their job, I found a problem in silent errors from eslint that slowed me down. I would like to share my experience hoping that ESLint could improve the debug experience for others.

At some point, where my numerous efforts weren’t bringing any fixing result on save, I decided to run eslint from my npm script ("lint": "eslint . --ext .ts --fix",)

This is when I discovered I had an obvious problem in my rules:

the true was wrapped in quotes. As soon as I resolved the problem, the on-save fixing started to work back again. I wasn’t aware that a problem in any of the rules syntax could make the whole thing go dead. So my question is - couldn’t ESLint be more helpful here, maybe scan the rules periodically and popup a warning?