docs(proxy): clarify setupProxy.js usage to fix 404 error in CRA v5#17080
docs(proxy): clarify setupProxy.js usage to fix 404 error in CRA v5#17080ginaseo wants to merge 1 commit into
Conversation
|
Hi @ginaseo! Thank you for your pull request and welcome to our community. Action RequiredIn order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks! |
|
Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Meta Open Source project. Thanks! |
What
Fixed a proxy issue in setupProxy.js where API requests were not forwarded to the target server (localhost:5000), resulting in a 404 error.
Changes
Replaced the app.use('/api', ...) pattern with pathFilter: '/api' in the proxy middleware configuration
Test
Confirmed that /api/... requests are correctly proxied to localhost:5000 using the following environment:
Reference
http-proxy-middleware official docs – Basic Usage