I regularly ask about CORS in interviews. The issue most developers have with CORS is that on a team, one person solves it for the team's local development and

I regularly ask about CORS in interviews. The issue most developers have with CORS is that on a team, one person solves it for the team's local development and maybe another person solves it for deployments. That is, most of the team never deals with it at all. > When everything in localhost/http you don't see any issues. I find the opposite to be true with React dev. You run an api on one port and your react app on another and get CORS errors. In a regular deployment, you just allow origins in the server and all is good. On localhost, every time you change/add a port, you have to allow another origin, play some proxy shenanigans, or run your browser without CORS.