This needs a trigger warning. I flashed back to upgrading a large project's build from node 12 to 16, which introduced a bunch of these in the scope of jest tes

This needs a trigger warning. I flashed back to upgrading a large project's build from node 12 to 16, which introduced a bunch of these in the scope of jest tests, and there was no indication of where the offending code was, which made the correct advice of "handle the rejections in some way" a little difficult.