David Hardy

As a workaround, I was able to temporarily just revert from `eslint": "^8.8.0`, to `eslint": "^7.32.0`. Then I could run `suppress-eslint-errors`, and immediately switch back to the latest eslint.

Nevermind, I found it. It's still a bug, but not spontaneous. Due to https://github.com/firebase/firebase-tools/issues/7268#issuecomment-2154523744 we have a backlog of changes piling up, and this issue was caused by one of...