Repository navigation
Trace requests through Next.js Axios proxies - #157
Open
passosiago wants to merge 1 commit into
Open
passosiago wants to merge 1 commit into
passosiago wants to merge 1 commit into
Conversation
Keep both HTTP hops on the map when a Pages Router catch-all forwards an Axios request to a uniquely matching backend. Follow the hooks that make the request in Screens and cover ambiguous routes with synthetic inventory fixtures.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 this changes
Links a browser request through a Next.js Pages Router catch-all to the backend handler. The scanner follows the Axios base path and the proxy's forwarding code when the backend has a unique matching literal route. Screens follows the request through nested hooks and shows the proxy between the browser call and the handler.
How I tested it
The synthetic example uses a Next.js inventory page and a NestJS API in separate repositories. It verifies that a browser request to
GET /api/relay/inventory/availabilitygoes through the catch-all toGET /inventory/availability. The regression tests also cover competing backend routes and more specific local routes.Checklist
npm testclaude plugin validate .CHANGELOG.mdupdated