Yes this just started popping up for me as well. Maybe because it takes me forever to update anything (when I finally let my machine reboot with updates it has collected)
CORB is a new security feature added to chrome and a few other browsers. It’s been a huge headache as the chrome dev team seems to believe that all json or text/html being passed between origins should be blocked.
There explanation even states that it will read the first couple of characters and block it if it “looks” like json or html.
Very very VERY lazy data protection. But because it completely tosses json out the window (keeps it from being stored in memory and is replaced by an empty object) we are going to have to find a way to receive data in a way that doesn’t scare the browser then parse it back into the format that we can work with (possible quick fix).
At least until the chrome dev team can show us how to “properly” handle cross origin communication among all the different frameworks that we use or until the developers maintaining these various web techs update the tech to chrome devs “security standards”.