Have you encountered this error?
This error occurs when working with APIs in your application code, and these bugs creep up every time you try to call the origin from another URL. The CORS errors stem from a security mechanism that the browser implements called the same-origin policy.
In this article, we will create our proxy CORS server hosting it on Heroku and have access to it any time we need it instead of using the generally hosted public URL used by everyone here on this with this link.
We will need the following to be installed on our system to begin.
Install the Heroku CLI.
For macOS, you can use homebrew. Visit heroku-cli for installation guides for your respective OS.
Install Node. Visit nodejs for installation guides.
Basic git version control skills
- Clone this repository to our local machine.
cd into the cloned repository and run npm install to install on the dependencies for the project.
Log into Heroku from the terminal.
- Create an app with the command Heroku create
After the app has been created and before deployment, Heroku will display a generic message with the deployed URL that you can use in place for the universal cors-anywhere URL.
- The last thing to do now is to push your newly created proxy server to Heroku
The CORS errors can be the bane of the frontend developer. But in this guide, we were able to spin up a proxy server from scratch using a Heroku server and basic git commands.
With these fixes, you'll never have to break a sweat overseeing the red CORS error in your browser, and you can confidently now have an error-free connection as a frontend developer.
Here is a valuable resource related to CORS