delete setupProxy.js file followup

[cevangel]

Description

This is a follow up PR to #484
Accidentally deleted the other one when trying to troubleshoot
Collaborated with @20jasper on troubleshooting

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change. Additionally, please include reasoning if tests have failed.

Type of change

Please select everything applicable. Please, do not delete any lines.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• This change requires an update to testing

Issue

• Is this related to a specific issue? If so, please specify:
• Closes delete setupProxy.js file #480 issue pull request
• Noting discrepency as I was told to do "git checkout development" but I don't see development branch, and I am seeing other people push to main branch.

Checklist:

• This PR is up to date with the main branch, and merge conflicts have been resolved
• I have executed npm run test and all tests have passed successfully or I have included details within my PR on the failure.
• I have executed npm run lint and resolved any outstanding errors. Most issues can be solved by executing npm run format
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings

[DevinCLane]

postposting this issue until after we migrate from Create React App to Vite

[DevinCLane]

now that we've finished the #474 is this PR good to merge or work on further?

[alcpereira]

postposting this issue until after we migrate from Create React App to Vite

It should be good now

[emmebravo]

@cevangel could you update your branch to be current with main and then reimplement the initial solution? thank you!

[cevangel]

@cevangel could you update your branch to be current with main and then reimplement the initial solution? thank you!

Just to make sure, to update my branch to be current with main, do the following right?:
git checkout your-branch-name
git fetch origin
git merge origin/main

Then do my initial solution from there?

[emmebravo]

@cevangel https://jtemporal.com/updating-a-branch-with-git-rebase/

make sure your forked main is up to date, and then follow the example I linked. lmk if you have questions.

[cevangel]

@cevangel https://jtemporal.com/updating-a-branch-with-git-rebase/

make sure your forked main is up to date, and then follow the example I linked. lmk if you have questions.

Got this error after making sure the forked main is up to date via this documentation, and did the example involving rebasing but got this error when running lint: not sure whether to do the reinstall or if that may result in other complications or if I just did something wrong on the way.

[DevinCLane]

duplicate #575