docs(proxy): clarify setupProxy.js usage to fix 404 error in CRA v5 #17080
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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