fix(node): handle node mount path in Request URL - #32
Merged
Bekacru merged 1 commit intoAug 9, 2025
Merged
Conversation
This was referenced Aug 20, 2025
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
2 participants
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.
This PR Fixes 404s when toNodeHandler is used inside an Express subrouter (e.g., mounted under /api). The Node adapter now constructs the full URL using req.baseUrl + req.url when baseUrl is present, preserving the mount path.
Related issue: better-auth/better-auth#3887
When mounted under a subrouter (e.g., /api), Express sets req.url to the route-relative path (e.g., /auth/...) and req.baseUrl to the mount path (e.g., /api). Previously, the adapter built the URL with base + req.url, which dropped the mount path.
before the patch
after the patch