We had the same problem in our project, where we ended giving up on using the CORS extension for the browser, that wasnt safe and didnt always work.
Instead we used angular CLI's built-in proxy config to reroute all calls to a remote location.
We did this by
A) creating a proxy-config.json file (see https://stackoverflow.com/a/39715785 )
B) and then run project with angular CLI using the following command:
ng serve --proxy-config proxy.conf.json
This way you trick you browser into "thinking" that you are accessing data from the same location, even though you aren't. And as a bonus you avoid using browser extensions that could be malicious.